find_and_attach_pdfs

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

The description discloses that the tool checks Unpaywall and attaches PDFs, and that items must have a DOI. However, with no annotations and no output schema, it fails to mention side effects (e.g., modifying the library), network behavior, rate limits, or what happens when no PDF is found. The dry_run parameter is documented in the schema but not in the description, leaving some behavioral gaps.

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 three concise sentences that are front-loaded with the core action and immediately provide the key prerequisite and a useful reference to a known feature. Every sentence adds value 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 simplicity of the tool (4 well-documented parameters, no output schema, no annotations), the description covers the essential purpose and the DOI constraint. It could be more complete by mentioning the dry_run option or expected return value, but the description is adequate for a straightforward fetch-and-attach operation.

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?

All four parameters are described in the schema (100% coverage), so the description does not need to add parameter details. The description does add a high-level context (DOI requirement) but does not go beyond the schema for parameter meaning, earning a baseline of 3.

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 a specific action ('check Unpaywall for open access PDFs and attach them') with a clear resource (Zotero items). It further specifies a prerequisite (must have a DOI) and distinguishes itself from sibling tools like import_pdf_to_zotero by pointing to the same source as Zotero Desktop's 'Find Available PDFs'.

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 on when to use the tool (for items with DOIs to find open access PDFs) and hints at its place relative to Zotero Desktop's feature, but it does not explicitly mention alternatives or exclusions relative to sibling tools like import_pdf_to_zotero or add_linked_url_attachment.

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