add_item_by_doi

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

No annotations provided, so description carries full burden. Discloses key behaviors: fetches metadata from CrossRef, checks duplicates by DOI, creates only if not exists. Good transparency, though lacks details on failure modes or auth requirements.

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?

Three concise sentences, each adding meaningful information: action, process, and condition. No redundant text, front-loaded with purpose.

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 tool with one parameter and no output schema, the description provides a complete workflow: fetch metadata, check duplicate, create if new. It could mention return value or error handling, but overall sufficient.

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?

Only one parameter 'doi', and schema has 0% description coverage. The description does not add extra meaning about the parameter format or constraints, but it explains how the DOI is used (fetch metadata and check duplicate), which provides context. The parameter is simple and self-explanatory from the tool name.

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?

Description clearly states the verb 'Add', resource 'item to Zotero library', and method 'by DOI'. Distinct from sibling tools like zotero_get_item (retrieve) and confirm_doi (confirm).

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?

Implies use when you have a DOI to add an item, but does not provide explicit guidance on when to use this tool versus alternatives, nor exclusion criteria. No mention of prerequisites or alternatives.

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