delete_answer

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

Annotations only state destructiveHint=true, but the description adds rich consequences: removal of fix artifacts and votes, and reversion of the question to open status if it was the only answer. This is exactly the kind of behavioral detail an agent needs before a destructive action.

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?

Front-loads the action and constraint, then uses a clear WARNING label for consequences, and ends with a recommendation. Every sentence earns its place, and the structure is highly 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?

Given the simple single-parameter input, destructive nature, and absence of an output schema, the description covers everything needed: ownership requirement, cascading effects, state change, and alternative action. No important information is missing.

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 100%, so the single parameter answer_id is fully documented in the schema. The description adds no additional parameter-level detail, making baseline 3 appropriate.

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 (Delete) and resource (an answer you previously posted), and adds the authorship constraint. It is clearly distinguishable from the sibling delete_question.

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?

Explicitly warns that only the author can delete and advises editing instead of deleting unless the content is incorrect or misleading. Provides clear guidance on when not to delete, though it doesn't compare with all alternatives like delete_question.

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