accessibility_declarations__delete

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false. The description adds no additional behavioral context beyond the verb 'Delete' and the HTTP endpoint. It does not mention that deletion is permanent or irreversible, nor any side effects (e.g., related data being removed).

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 a single, front-loaded sentence that immediately conveys the operation. It efficiently includes the REST endpoint without wasting words.

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 simple delete operation with one parameter and full schema coverage, the description plus annotations are sufficient. The agent knows it's destructive (via annotations), what parameter to supply (via schema), and the endpoint (via description). It's missing only minor context like destructiveness wording, but the annotations cover that.

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% because the 'id' parameter is described as 'ID from the matching list call.' The tool description itself adds no additional parameter detail, so the baseline of 3 applies since the schema already carries the semantic load.

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 'Delete an accessibility declaration,' which is a specific verb+resource combination that distinguishes this tool from its siblings (create, get, update, list). The endpoint is also provided for clarity.

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?

No guidance is given on when to use this tool versus alternatives. It doesn't mention that this permanently removes the declaration or that the ID should come from a list call (though the schema does). There is no mention of when not to use it or any prerequisites beyond the parameter description.

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