Zotero attachments (files)

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

Annotations only provide readOnlyHint=false and openWorldHint=true. The description adds crucial behavioral details: file bytes are read/written to disk (not streamed), and operations use cloud Web API and consume storage quota. This goes beyond annotations.

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 focused paragraph with front-loaded purpose and action breakdown. It is concise but could benefit from bullet-point structure for the three actions to improve scannability.

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 complexity (9 parameters, 3 actions, no output schema), the description covers action behaviors, key parameter roles, and file handling. Return values are mentioned for upload and download but not explicitly for info, which is a minor gap.

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?

With only 44% schema description coverage, the description compensates well by explaining which parameters apply to which action (e.g., parent_item for upload, item_key for download/info) and their roles. It adds meaning beyond the bare 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 clearly states the tool handles attachment files with three specific actions: upload, download, and info. It uses specific verbs and distinguishes itself from sibling tools like zotero_get_item and zotero_fulltext by focusing on file operations.

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 explains each action's purpose and associated parameters, providing clear context for when to use each. It does not explicitly compare to sibling tools, but the action-oriented structure and mention of alternatives are sufficient.

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