Push a full problem into a draft

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description says test cases are appended to whatever the draft already holds, implying repeated identical calls would keep adding test cases and thus change state. This contradicts the idempotentHint=true annotation, which states the operation is idempotent. No other behavioral context is added beyond that, and the contradiction is severe.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is only two sentences long, front-loads the core purpose, and uses the second sentence to point to the alternative. Every sentence earns its place, with no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description gives the main behavior and a clear pointer to the alternative, and the output schema exists to clarify returns. However, the idempotency contradiction is unresolved, and the description does not clarify whether metadata and statement are overwritten or merged when writing into an existing draft, leaving an important usage gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all parameters. The description adds only minimal context by noting problem_json contains metadata, statement, and optionally test cases, which mostly overlaps with the schema description and does not significantly deepen parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action 'Write a problem object into an existing draft' and enumerates the components: metadata, statement, and optionally test cases. It also differentiates itself from the sibling tool repovive_build_author_complete_problem by naming what that tool does instead.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly explains when to use this tool versus the alternative: it appends test cases, and for a complete import that clears old cases and uploads reference solution, editorial, and validator, the agent should use repovive_build_author_complete_problem. This gives clear when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.