Delete Annotation

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds the crucial context of 'permanently,' indicating irreversible removal, which goes beyond the mere destructive hint. However, it does not elaborate on side effects or permissions.

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 a single, front-loaded sentence with no filler or redundant information. Every word adds value, making it highly concise and efficient.

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 simple delete operation with one parameter and an output schema, the description is minimally adequate. It conveys the core action but lacks parameter elaboration and explicit usage guidance, which are important for a destructive tool.

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 schema shows one parameter, annotation_key, with 0% description coverage. The description does not explain how to provide or format the key, relying entirely on the parameter name for meaning. Since coverage is low, the description should have compensated but did not.

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 explicitly states 'Permanently delete a Zotero annotation,' giving a clear verb ('delete'), resource ('Zotero annotation'), and scope ('permanently'). It distinguishes itself from siblings like delete_note and trash_item by specifying the annotation type and irreversible nature.

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 word 'permanently' implies irreversibility compared to trash_item, but the description does not explicitly state when to use this tool versus alternatives or mention any exclusions. Usage context is inferred rather than clearly presented.

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