Delete Annotation

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

Annotations already mark this as destructive (destructiveHint: true), and the description reinforces that with 'Permanently delete.' It adds behavioral context by explaining how library targeting behaves differently from the default, which is useful beyond what the annotations convey. No contradiction with annotations exists.

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, front-loaded with the core action, and contains no filler. Every sentence earns its place: the first states the purpose, and the second gives essential library-targeting behavior.

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 single-resource deletion tool with an output schema and clear annotations, this description is complete. It covers purpose, permanence, the required key concept, and the non-obvious library targeting rule. Nothing needed to safely invoke the tool is missing.

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 0%, so the description carries the burden of explaining parameters. It meaningfully explains library_id and library_type as a paired targeting mechanism and describes their default behavior. annotation_key is left to the schema, but its required status and title make it self-explanatory.

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 states a specific verb and resource: 'Permanently delete a Zotero annotation.' This clearly distinguishes it from sibling deletion tools like delete_item, delete_note, and delete_collection by naming the exact object type. The word 'permanently' also adds helpful severity context.

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 gives clear usage context by specifying when the operation applies (deleting an annotation) and provides practical routing guidance for libraries: pass both library_id and library_type to target another library, or omit both for the default. It does not explicitly compare against alternatives, but the resource type makes the intended use unambiguous.

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