zotero_import_identifier

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

With no annotations, the description carries the burden of behavioral disclosure. It mentions metadata sources (CrossRef/Open Library) and auto-detection of identifiers, which is useful. However, it does not disclose side effects (e.g., permanent creation, potential duplicates, or setup requirements) that would be valuable for a write operation.

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 compact and well-structured: a clear one-sentence summary, a brief usage context, and an Args list with examples. Every sentence adds value and the structure front-loads the most critical information.

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 relatively simple tool with three parameters and an output schema, the description covers purpose, usage context, and parameter semantics thoroughly. It could mention prerequisites like Zotero setup or potential failure modes, but the description is sufficient for typical use cases.

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 provides meaningful semantics for all three parameters: specific examples for 'identifier', and clear definitions for 'collection_keys' and 'tags'. This goes well beyond the bare schema, which only supplies types and titles, making the tool much easier to invoke correctly.

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 states a specific action: 'Look up a DOI, arXiv id or ISBN and save it as a Zotero reference.' This clearly distinguishes it from sibling tools like zotero_search or zotero_create_item by focusing on importing via identifiers.

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 explicitly says 'This is the fastest way to add a source you have a citation for,' giving clear context on when to use it. It does not explicitly name alternatives or state when not to use it, but the context implies it should be used over manual creation or searching.

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