Zotero Get Attachment Path

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

No annotations are provided, so the description carries the full burden. It discloses that the tool is 'Local mode only' and returns paths rather than content, which is useful. However, it does not mention potential error cases (e.g., item has no attachments), whether multiple paths are returned (though 'path(s)' implies it), or any permissions/requirements. The description adds some context but lacks rich behavioral detail expected for a tool with no annotation coverage.

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 two sentences with no wasted words. The primary function is stated first, followed by the use case. It is efficient and front-loaded, making it easy for an agent to parse quickly.

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 the tool's simplicity (one parameter, output schema present), the description covers the main purpose and a key use case. It mentions the local-only constraint and the alternative to fulltext. However, it does not address edge cases like missing attachments or whether it returns all paths or just one. Since an output schema exists, the return structure is not required in the description, but a bit more context on prerequisites or error behavior would improve completeness. Overall, it is adequate for a simple getter.

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, and the description does not explain the single parameter 'item_key' at all. It does not add any meaning beyond the parameter name itself. Since the schema provides no description, the description must compensate, but it fails to do so, leaving the agent to infer the parameter's purpose from the tool name alone.

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 function: returning local filesystem paths of a Zotero item's attachments. It specifies the resource (attachments) and the verb (return), and distinguishes it from the sibling zotero_get_item_fulltext by noting the use case for large PDFs. This makes the purpose unambiguous and differentiates it from related tools.

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 provides a when-to-use scenario: 'Useful when you want to read a large PDF directly (e.g., a book) instead of going through zotero_get_item_fulltext, which is page-limited.' It names the alternative tool and the condition that selects this one, giving clear guidance on when to use it versus the sibling.

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