import_to_zotero

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

With no annotations, the description carries the full burden. It discloses key behaviors: creating an item, adding a linked-file attachment, preserving the PDF locally, and reusing an existing item if the DOI is already present. However, it omits details about return values, error handling, or behavior when no DOI is provided.

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 single, well-structured sentence that front-loads the main action and then provides key details. It contains no fluff and is appropriately sized for the tool's complexity.

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 12 parameters, no annotations, and no output schema, the description is far too sparse. It does not explain the return value, detail the DOI reuse process, or provide any guidance on what metadata fields are expected. The tool is more complex than the description adequately covers.

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 only 17%, so the description must compensate. It only hints at pdf_path and collection_name via mentions of PDF and Collection, while the other 10 parameters (title, authors, journal, etc.) receive no explanation. This leaves most parameter semantics unclear.

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 specifies the action: import a paper into Zotero, including creating an item, attaching a linked PDF file, and assigning it to a Collection. It also differentiates from siblings by bundling these operations and noting DOI-based reuse.

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 implies the tool is used for importing papers into Zotero, but it does not explicitly state when to prefer this over alternatives like create_collection or search_zotero_library. The context is clear enough but lacks explicit exclusions or alternative guidance.

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