attach_pdf

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

Beyond the annotations, the description discloses meaningful side effects: it can auto-download a PDF via Unpaywall/PMC/bioRxiv or accept a local file path. This is useful external-behavior context. It stops short of detailing failure or duplicate behavior, but annotations already signal mutating and non-idempotent behavior.

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 two sentences with no filler. It front-loads the core action, then explains usage modes, then gives an explicit trigger. Every sentence earns its place.

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 relatively simple tool with an output schema, the description covers the main input modes and use case well. The only notable omission is guidance on what happens if both doi and pdf_path are supplied, but that is a minor gap given the rest of the definition.

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?

The schema has 0% property description coverage, so the description must help interpret parameters. It maps doi to the auto-download capability and pdf_path to the local-file option, but it never explicitly refers to parent_key or explains the relationship or precedence of doi vs pdf_path. Property names help, but the description only partially compensates for the schema gap.

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 opens with a specific verb and resource: 'Attach a PDF to a Zotero item.' It clearly distinguishes this from read-only sibling tools like get_item_attachments by focusing on adding an attachment, and it further clarifies the two input modes (auto-download vs local file path).

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 gives an explicit trigger: 'Use this when the user wants to add a PDF to a paper that doesn't have one.' This is a clear usage context, though it does not explicitly name alternative tools or state when not to use it.

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