zotero_upload_file

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that the operation creates a new child attachment, uploads the file, and fails if the attachment already has a stored file. This is meaningful and goes beyond merely saying 'upload file'. It does not discuss permissions or reversibility, but for this tool the core side effects and failure condition are 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 deliver the essential behavior, both invocation modes, the failure case, and the scope restriction. The information is front-loaded and every clause earns its place with no redundancy or filler.

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 4 parameters, 100% schema coverage, and an output schema, the description is nearly complete. It clarifies the item_key semantics, the failure mode, and the supported vs. unsupported attachment types. It could mention that the filepath must be locally accessible, but this is minor because the schema already calls it an absolute path and the core usage context is well covered.

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%, so the baseline is 3. The description adds real value by explaining that item_key can be either a parent item key or an existing attachment key, and that the latter triggers a different code path with a failure condition. It also clarifies the supported attachment type, which gives the agent a better mental model than the raw schema 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 uses a specific verb and resource: 'Attach a local file to an item' and clarifies the exact behavior of creating a stored-file child attachment and uploading the file. It also distinguishes the two invocation modes (parent item key vs. existing attachment key), which makes the purpose unambiguous and differentiates it from sibling tools like zotero_download_file and zotero_create_item.

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 provides clear context for when the tool applies: it is supported for imported-file attachments and explicitly excludes linked URLs. It also explains how passing an attachment key changes the behavior and warns that it fails if a file is already stored. It does not name a specific alternative tool for linked-URL cases, so it stops short of full 5-level guidance.

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