Delete a Forms answer

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing that the deletion is recoverable via answers_restore, which annotations cannot express, though it says nothing about permissions or side effects on exports/aggregates.

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?

A single front-loaded clause stating the action, followed immediately by the recovery path. Zero padding; every clause earns its place.

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 two-parameter destructive call with full schema coverage and annotation-backed safety hints, the description gives an agent what it needs: what it destroys, at what granularity, and how to undo it. Minor omissions (permission requirements, effect on derived data) keep it from being exhaustive.

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%, with both required parameters documented in-schema (answer_id sourced from answers_list, survey_id as 24-char hex). The description adds no parameter-level detail, so the baseline of 3 is 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 a precisely scoped resource (one answer of a form), leaving no ambiguity about granularity. It also names the recovery counterpart answers_restore, which lets an agent distinguish this from restore-style siblings without opening either 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?

Provides clear context that this is the removal path and that answers_restore is the inverse operation, implying when to reach for each. It stops short of explicit when-not guidance (e.g., when to prefer restore, or what happens if the answer id is unknown).

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