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

With no annotations, the description carries the full burden and does real work: it discloses the 7-day waiting requirement, that the submission 'can never be awarded', and that 'its content stays sealed' — a meaningful consequence statement for an irreversible mutation. It omits what happens to your slot/standing afterward, whether withdrawal can be undone, and any auth or rate-limit notes beyond the schema's api_key hint.

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?

Three short sentences, zero filler: eligibility and effect first, situational guidance last. Every sentence adds information the agent cannot get from the schema.

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?

For a 2-parameter mutation with no annotations and no output schema, the description covers eligibility, irreversibility, and motivation — enough to call it correctly. The remaining gap is post-call consequences (does the slot free up, can the content be recovered by you), which a mutation tool ideally would state.

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 coverage is only 50%: api_key is documented in the schema but submission_id is a bare string. The description compensates partly by constraining which submissions qualify (pending, own, 7 days unreviewed), which helps the agent pick the right id, but adds no format or lookup guidance for submission_id itself.

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?

States a specific verb and resource ('Withdraw your own pending submission') plus the eligibility condition (7 days without review). The phrase 'your own' implicitly separates it from reviewer-side siblings like decline_submission, but no sibling is named explicitly, leaving the agent to infer the contrast.

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?

Gives a clear situational trigger: 'Use this when a poster has gone quiet and you would rather stop waiting,' and states the precondition of 7 unreviewed days. It does not name an alternative action (e.g., messaging the poster first, or declining via a poster-side tool), so exclusions remain implicit.

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