Upload a file to a Zotero attachment

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

Annotations only declare readOnlyHint=false and openWorldHint=true. The description adds genuinely useful behavior: idempotency via MD5 dedup ('Files already stored with the same MD5 are left unchanged') and a hard 100 MB upload limit. It does not describe auth requirements or what happens on partial/failed uploads, so it falls short of a 5.

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?

Front-loaded with the core action, then prerequisites and limits in short chunks. The enumeration of creation fields ('itemType attachment, linkMode imported_file, parentItem, and contentType') is a slight tangent belonging to the sibling tool, but overall it is tight and well ordered.

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?

An output schema exists, so return values need no explanation. For a two-parameter upload tool the description covers the workflow prerequisite, the size ceiling, and the dedup rule, which is everything an agent needs to invoke it correctly.

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 100%, so both parameters are already documented in the schema, making 3 the baseline. The description's mention of itemType/linkMode/parentItem/contentType pertains to the prerequisite zotero_api call rather than to this tool's own arguments, so it adds little parameter-level meaning.

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 first sentence gives a specific verb (store/upload), resource (a local file), and target (an attachment item via the Web API upload flow). It is clearly distinguishable from sibling zotero_api, which is identified as the tool that creates the attachment instead of uploading the bytes.

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 names the prerequisite ('Create the attachment first with zotero_api'), which routes the agent correctly between the two tools. It lacks an explicit when-not-to-use condition (e.g. what to do for non-imported_file link modes), but the context provided is clear and actionable.

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