zotero_search_by_citation_key

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

No annotations are provided, so the description carries full burden. It discloses behavior: returns metadata or not-found message, details local mode (queries BBT API) and web mode (scans Extra field, slower, may miss items), and requires the Better BibTeX plugin. No contradictions.

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 moderately sized but every sentence contributes useful information. It front-loads the core purpose and then adds behavioral details and alternatives. Minor redundancy could be trimmed but overall 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?

Given no annotations, a single parameter with high schema coverage, and an output schema (not shown but referenced), the description covers all necessary context: purpose, parameters, modes, prerequisites, limitations, and alternatives. It feels complete for an agent to use correctly.

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 100% for the single parameter. The description adds value by noting case-sensitivity and the exact key format required, as well as providing an example. This goes beyond the schema's basic 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?

The description starts with 'Look up a single Zotero item by its BetterBibTeX citation key', which clearly states the verb (look up), resource (Zotero item), and identifier. It also differentiates from sibling tool zotero_search_items by explicitly mentioning alternatives for partial-key lookup.

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 provides explicit guidance: use for exact citation key lookup, and for partial-key/free-text lookup use zotero_search_items. It also explains two modes (local vs web) and prerequisites (Better BibTeX plugin). An example call is included.

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