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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the context that the document is live and that a token is required, but doesn't elaborate on side effects or irreversibility. This adds modest value but doesn't fully round out the behavioral picture.

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 compact and well-structured: the first sentence states the core action, the second gives a practical prerequisite and authentication note. No unnecessary words or repetition.

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, fully described schema, and rich annotations, the description covers the essential context: the operation, how to prepare (get IDs), and authentication. It lacks error-handling or return-value details, but these are not critical for a delete operation with no output schema.

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?

The input schema already provides 100% coverage with detailed descriptions for all 5 parameters. The tool description references annotation IDs and tokens but does not add semantic meaning beyond what the schema defines, so a baseline score 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?

The description clearly states the tool's function with a specific verb ('Removes'), resource ('text annotation'), and scope ('live Trident document'). This immediately distinguishes it from sibling tools like add_annotation, update_annotation, and delete_connection/container/node.

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?

It provides actionable guidance: 'Use get_document_summary to get all annotation IDs before calling this' and notes the prerequisite of a valid editor access token. While it doesn't explicitly name alternatives or exclusions, the indicated workflow makes the appropriate usage context clear.

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