delete_annotation

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

The description states the tool deletes an annotation and provides a dry_run parameter to preview without executing. However, it does not disclose other behavioral traits such as irreversibility, required permissions, or return value. With no annotations, more detail could be beneficial.

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 concise, with a single sentence for the action and three lines for parameter descriptions. Every sentence provides unique information without repetition or fluff.

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 tool's simplicity and the presence of an output schema (not shown), the description covers the core functionality, parameters, and a dry_run option. It lacks details on preconditions or error handling, but is sufficiently complete for its complexity.

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?

Since schema description coverage is 0%, the description fully compensates by explaining each parameter: layer_id (annotation layer ID), annotation_id (annotation ID to delete), and dry_run (preview without executing). This adds essential meaning beyond the schema.

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 verb 'Delete' and the resource 'a specific annotation from an annotation layer'. It distinguishes from sibling tools like delete_annotation_layer (which deletes the entire layer) and create_annotation (creates).

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?

The description implies that the tool is used for deleting a single annotation, requiring layer_id and annotation_id. It does not explicitly state when not to use it or provide alternatives, but the context is clear.

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