zotero_delete_note

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

With no annotations, description carries full burden. It explains non-destructive nature, recoverability, inability to permanently delete via API, and mode requirements. Also warns about consequences of wrong key usage. All behaviors clearly disclosed.

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?

Every sentence serves a purpose: main action, non-destructive note, parameter guidance, scope limitation, mode requirement, example. Front-loaded with key info. Efficient and well-structured.

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?

With one parameter, full schema coverage, and no annotations, the description covers purpose, usage, behavioral traits, parameter semantics, prerequisites, and exclusions. Output schema exists, so return value explanation is not needed. Highly complete for the tool's complexity.

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 has 100% coverage but description adds critical context: item_key must be the note's own key (not parent), advises how to find it, and provides an example. This goes beyond the schema's basic type description.

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?

Clearly states the action (Move to Trash) and resource (note). Explicitly scopes to notes only, distinguishing from deleting items, collections, or attachments. Also clarifies non-permanent nature vs permanent deletion.

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?

Provides explicit when-to-use (trashing notes), when-not (for permanent deletion, use UI). Gives prerequisite steps (find note key using get_notes/search_notes). Warns against using parent item key. Specifies required library mode (writable, not local-only).

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