zotero_download_file

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

With no annotations, the description carries the behavioral burden and does provide useful non-obvious detail: only imported_file attachments work, link-mode attachments have no file, and a parent item auto-selects its best attachment. The main gap is that 'best' is underspecified and no overwrite/path behavior is disclosed.

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?

Two sentences with no filler. The core action is front-loaded, and the attachment-type constraint and exception are packed efficiently into the second sentence.

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 two-parameter download tool, the description covers selection mode, destination, applicable attachment type, and a key limitation. An output schema exists for return details. Minor ambiguities around 'best attachment' and file overwriting prevent a perfect score.

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 coverage is 100% and both item_key and save_path already have meaningful schema descriptions. The description reinforces item_key's parent-item behavior but adds no new semantic or format constraints beyond the schema.

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 uses a specific verb and resource: 'Download an item's stored attachment file from Zotero to a path on disk.' This clearly distinguishes it from sibling tools like zotero_upload_file or zotero_item_metadata, which deal with uploading or non-file data.

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?

It explicitly states when the tool applies: 'Works for imported_file attachments' and when it does not: 'Link-mode attachments have no stored file.' It does not explicitly name alternative sibling tools, but the usage context and exclusion are clear.

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