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

Annotations already cover readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is partly given. The description adds genuinely new behavior: no reviewer acts afterwards, the submission cannot be reopened, the action is audited, and dry_run is on by default and merely validates ownership plus open state. That is meaningful consequence disclosure beyond the structured fields.

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 core action and its precondition are front-loaded, followed by the consequence, the ownership constraint, and the dry-run note. It is dense but every clause carries information; the telegraphic fragments ('Audited.', 'Only your own, whatever the key’s role.') are terse yet readable.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety flags. Combined with the stated preconditions, irreversibility, audit trail, and dry-run behavior, an agent has everything needed to invoke this two-parameter tool correctly.

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 baseline is 3, but the description adds meaning the schema lacks: it explains that dry_run reports whether the submission is yours and still open, i.e. what the preview actually validates, and reinforces that id must refer to the key's own submission.

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 — withdrawing one of the key's own submissions — plus the scoping condition (still open, own account only). An agent can distinguish this from review_submission, comment_on_my_submission, or list_my_submissions without opening any schema.

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 clear preconditions: the submission must still be open (awaiting a reviewer or your answer), it must belong to the key's account, and the key's role doesn't matter. It stops short of naming alternatives such as review_submission for cases where the submission is no longer open, so it is strong context rather than an explicit when-not routing.

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