attach_pdf

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

With no annotations, the description carries full burden. It explains the download from URL/local path, creation of Zotero item from supplied metadata, PDF attachment, on-demand collection creation, and optional send-to-reader. It does not detail duplicate handling or error behavior, but covers core behavioral traits adequately.

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 front-loaded with the main action and is structured logically. Each sentence adds value, but it is somewhat dense and could be more concise by grouping related info. Still, it avoids wasted words.

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?

The description covers the tool's purpose, input expectations, and behavior well. With an output schema present, return values need not be explained. It mentions the prerequisite 'Requires Zotero' and contrasts with queue_papers. Minor gaps remain regarding error conditions and idempotency, but overall it is sufficiently complete.

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 0%, so description must compensate. It adds context for item_type (lists valid values), send (delivers to e-reader), collections (created on demand), and url_or_path (explains http(s) or local). However, it omits doi and year parameters entirely, and does not systematically describe each field.

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 ingests a PDF into Zotero with attachment, specifies it's for grey literature, and distinguishes itself from sibling tool queue_papers by noting it does not queue. The verb 'ingest' and resource 'PDF into Zotero' are specific and actionable.

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 explicit use cases (grey literature, no registry indexes) and contrasts with queue_papers. It also mentions using 'book' item type for open-access textbooks. However, it does not explicitly exclude other sibling tools like add_book or list alternative scenarios, so some guidance is missing.

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