Add Papers By Dois

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

Annotations already provide readOnlyHint=false and destructiveHint=false, so the description only adds the batch limit (up to 50) and the optional collection key. It does not disclose behavior on duplicate DOIs, partial failures, or how invalid DOIs are handled. With annotations present, the added value is some but not rich.

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 concise: one clear sentence plus a brief parameter list. No unnecessary words; every piece adds value. It is well-structured with the batch note upfront and parameters listed succinctly.

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?

The tool is a batch operation with 3 parameters and an output schema, yet the description does not mention attach_pdfs, error handling, or what the tool returns (though output schema exists). It covers the core action and two parameters, but for a batch tool with possible edge cases, more context (e.g., duplicate handling) would be beneficial.

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 schema has 0% description coverage, so the description must compensate. It explains dois as 'List of DOIs to add' and collection_id as 'Optional Zotero collection key', but it omits attach_pdfs entirely. The two mentioned parameters are given clear semantic meaning, but the missing parameter is a gap.

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 tool's purpose: 'Add multiple papers to Zotero by their DOIs' with the batch context 'up to 50'. It distinguishes from sibling add_paper_by_doi by explicitly mentioning 'multiple' and 'batch', making the divergence clear.

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 phrase 'batch, up to 50' implies this is for adding multiple papers at once, contrasting with the singular sibling add_paper_by_doi. However, it does not explicitly state 'use this for multiple DOIs, use the singular tool for one', nor does it mention when not to use it. The context is clear though not fully explicit.

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