⚠️ Delete a review answer

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

Beyond the destructiveHint annotation (which only flags destructiveness), the description adds critical context: deletion is irreversible, immediately removes the public answer, and returns a success flag. This fully discloses behavioral traits.

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 succinct: two sentences plus a warning, with essential information front-loaded (action, irreversibility, alternative). Every sentence serves a purpose without waste.

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 covers the core behavior (destructive, irreversible, success flag return). Parameter schema fully covers inputs. A minor gap is that the success flag structure is not described, but for a simple deletion tool this is acceptable.

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. The description does not add any additional meaning beyond what the input schema already provides for parameters like answer_id, dryRun, and idempotencyKey.

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 ('permanently deletes') and the resource ('review answer'), and the title adds 'Delete a review answer'. It distinguishes from sibling tool reviews_create_review_answer_v1 by mentioning the alternative for publishing again.

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 instructs to confirm the action with the user, warns of irreversibility, and points to reviews_create_review_answer_v1 as an alternative for publishing a new answer. Provides clear when-to-use and when-not-to-use context.

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