Delete Item

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

Annotations already flag destructiveHint=true, but the description adds critical context: the deletion is 'permanent' (beyond mere destruction) and applies to an 'item' as opposed to notes/annotations. It does not detail side effects like cascading attachment deletion, but given annotation coverage, this is acceptable.

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 short and front-loaded with the core action. However, the 'Args:' section duplicates the input schema, which is unnecessary and slightly verbose. Still, it remains compact and readable.

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 one-parameter destructive tool with an output schema and clear annotations, the description covers the essential purpose, permanence, and parameter meaning. It doesn't elaborate on return values (covered by output schema) or all potential side effects, but that is not critical given the tool's simplicity.

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 description restates the parameter as 'The Zotero item key to delete', which adds minimal meaning over the schema's 'Item Key'. With 0% schema description coverage, it provides basic clarification but no format, example, or edge-case guidance. The param is simple and self-explanatory, so this is adequate.

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 'Permanently delete an item from your Zotero library' — a specific verb, resource, and scope. It distinguishes from siblings by specifying 'item' (not note/annotation) and 'permanently' (contrasting with trash_item/restore_item).

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 explicit when-to-use or alternatives are mentioned. The word 'permanently' implies a contrast with trash_item, but the description does not explicitly guide the agent to use trash_item for reversible deletions or delete_note for notes. Usage is implied rather than stated.

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