delete_annotation

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered by structured data. The description adds nothing beyond restating the deletion: no indication that the removal is permanent, whether it requires write permission, or whether deleting the note affects the annotation object itself.

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 sentence with zero filler. It is arguably too terse for a destructive mutation tool, but nothing in it is wasted.

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 destructive, non-idempotent mutation with no output schema and an ambiguous sibling (manage_annotation), the description is too thin: it omits reversibility, permission requirements, and any routing guidance to the correct sibling.

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 coverage is 67%: bibcode and library_id are described in the schema, while response_format has only an enum and default with no description. The description mentions the document/library context but adds no parameter-level meaning, so it neither compensates nor regresses.

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 resource (annotation/note) scoped to a document in a library, so the core action is unambiguous. However, siblings get_annotation and especially manage_annotation exist, and the description does nothing to distinguish this targeted delete from whatever manage_annotation covers.

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 when-to-use guidance, no prerequisites, and no named alternative despite manage_annotation sitting in the sibling list. The agent must infer that this is the single-annotation delete path rather than the bulk/management path.

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