zotero_read_pdf_pages

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

With no annotations, the description must disclose behavioral traits. It mentions pages are 1-indexed, the need for PyMuPDF, and reads a range. However, it says 'page range(s)' while the schema only supports a single contiguous range, and it does not specify error handling for invalid pages or bounds, leaving some ambiguity.

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 extremely concise: two sentences plus a dependency note. The first sentence states the purpose, the second gives usage context, and the third provides a setup requirement. No redundant 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 simplicity (3 params, output schema exists), the description covers essential usage points. It explains when to use, page indexing, and dependency. However, it does not summarize the return type, which the output schema might provide, and the plural 'range(s)' is slightly misleading.

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 already covers all parameters (100% coverage). The description adds value by clarifying that pages are 1-indexed and that omitting end_page reads only start_page. It also mentions the PyMuPDF dependency, which is not in the schema.

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 reads specific page ranges from a PDF attachment of a Zotero item. It distinguishes itself from related tools like zotero_get_item_fulltext by focusing on page ranges and referencing the PDF outline tool.

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 explicitly says when to use the tool (when you know which pages to read) and provides an example scenario (after getting the PDF outline). It does not explicitly state when not to use it or list alternatives, but the context is clear.

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