zotero_read_pdf

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: it finds the first PDF attachment (implying it may skip others), reads from the local file system (suggesting file access requirements), and returns full text. However, it lacks details on error handling (e.g., if no PDF exists), permissions needed, or performance aspects like rate limits. It adds value but is not comprehensive.

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 core action and resource. It efficiently covers the tool's purpose, parameter context, and outcome without any wasted words. Every part earns its place by contributing essential information.

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 tool's moderate complexity (involving file system access and PDF parsing), no annotations, and an output schema (which handles return values), the description is mostly complete. It explains what the tool does and the parameter's role. However, it could improve by mentioning potential failures (e.g., no PDF found) or dependencies, but the output schema likely covers return structure, so it's adequate.

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 input schema has 0% description coverage, providing no details about 'itemKey'. The description fully compensates by explaining that 'itemKey' specifies the item in the Zotero library whose children are searched for PDF attachments. This adds crucial meaning beyond the bare schema, making the parameter's purpose and usage clear.

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 specific action ('find the first PDF attachment, read it from the local file system, and return its full text') and the resource ('children of the item specified by itemKey in the Zotero library'). It distinguishes from sibling tools like 'read_pdf' (general PDF reading) and 'zotero_get_item'/'zotero_search_items' (item retrieval/search) by focusing on PDF extraction from Zotero attachments.

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 usage when you need to extract text from a PDF attached to a Zotero item, but it does not explicitly state when not to use it or name alternatives. For example, it doesn't clarify if 'read_pdf' should be used for non-Zotero PDFs or if 'zotero_get_item' is better for metadata-only access. The context is clear but lacks explicit exclusions.

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