create_item_from_doi

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

With no annotations provided, the description carries full burden. It mentions 'auto-fills metadata' which is useful behavioral context, but doesn't disclose other important traits like whether this is a write operation (implied by 'Create'), what happens on failure, permission requirements, rate limits, or what the created item contains. More behavioral details would help the agent.

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 a single, efficient sentence that front-loads the core purpose. Every word earns its place with no redundancy or unnecessary elaboration.

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 creation tool with 3 parameters (1 required), 0% schema coverage, no annotations, but with an output schema, the description is minimally adequate. The output schema likely covers return values, but more guidance on parameter usage and behavioral context would improve completeness.

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 0%, so the schema provides no parameter descriptions. The description mentions 'DOI' which maps to the required 'doi' parameter, but doesn't explain the optional 'collections' or 'tags' parameters at all. It adds minimal value beyond what's inferable from parameter names.

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 the action ('Create a Zotero item'), the input source ('from a DOI'), and the key behavior ('auto-fills metadata'). It distinguishes itself from sibling tools like 'create_item' by specifying the DOI-based creation method.

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 implies usage when you have a DOI and want to create an item with auto-filled metadata, but it doesn't explicitly state when to use this versus alternatives like 'create_item' (manual entry) or 'import_bibtex' (BibTeX import). No exclusions or prerequisites are mentioned.

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