zotero_pdf_text

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

No annotations are provided, but the description mentions 'Cheap compared with rendering pages' and suggests a workflow. This gives some insight into performance characteristics and intended usage, but it does not disclose side effects, permissions, or rate limits. The read-only nature is implied but not explicit.

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 concise, consisting of two short sentences that effectively convey the purpose and usage guidance without unnecessary detail. It is well-structured and front-loaded.

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 (two parameters, one required) and the presence of an output schema, the description provides enough context for basic usage. However, the lack of parameter explanations and output format details leaves some gaps. The workflow hint partially compensates, but overall it is not fully 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?

The schema provides no descriptions for the parameters (item_key and pages), and the description does not explain what they mean or their expected formats. With 0% schema description coverage and no additional context, the agent has insufficient information to correctly populate these parameters.

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 'Extract text from an item's PDF' with a specific verb and resource, and it distinguishes itself from the sibling tool zotero_pdf_pages by focusing on text extraction rather than rendering pages.

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 guidance: 'use this first, then zotero_pdf_pages for the pages whose figures matter.' This tells the agent when to use this tool and when to switch to the alternative, making the usage context clear.

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