delete_annotation

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

Annotations already mark destructiveHint=true, so description correctly implies destructive action. But it adds no additional behavioral context such as whether deletion is permanent, requires specific permissions, or has cascading effects. Minimal value beyond annotations.

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?

Two sentences; the first sentence is unnecessary context about annotations in general and could be removed. The core deletion instruction is clear but could be more concise.

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?

No output schema, so description should cover return behavior, error cases, or side effects. It leaves these unaddressed. For a destructive operation, more context is needed for safe invocation.

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?

Input schema covers 50% of parameters (customerContext has a description, id does not). The description merely references 'the Id' but does not explain the id parameter format or the optional customerContext. Schema coverage baseline is 3, and description adds little.

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 'Deletes the annotation specified by the Id,' specifying the verb and resource. It distinguishes from sibling tools like create_annotation, update_annotation, get_annotation, and list_annotations. However, the first sentence about 'Custom notes added to cost data' is redundant and may confuse, preventing a perfect score.

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 on when to use this tool versus alternatives like update_annotation or list_annotations. The description does not provide context on prerequisites, idempotency, or typical use cases.

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