Zotero Read Pdf Pages

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

With no annotations, the description carries the full behavioral burden, and it delivers: pages are 1-indexed, text output preserves headings and flags garbled equations/figures/tables, image output returns PNGs up to 10 pages, and rect uses normalized 0-1 coordinates and zooms into start_page. This goes well beyond a generic 'read PDF' statement and tells the agent what to expect.

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?

Three dense, purposeful sentences front-load the core action, then cover the text format, image format, and rect behavior without repetition. No filler or redundant restating of the schema is present.

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?

For a 5-parameter, no-output-schema tool with no annotations, the description is remarkably complete: it covers when to use it, what both formats return, page indexing, image limits, and the rect coordinate convention. An agent has enough information to invoke the tool and interpret the result correctly.

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 coverage is 100%, so the baseline is 3, but the description adds meaningful meaning: it explains that pages are 1-indexed, that rect coordinates are normalized 0-1 and can come from zotero_get_page_layout, and that image output is capped at 10 pages. This is useful context beyond the raw schema field descriptions.

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 opens with a specific verb and resource: 'Read specific page range(s) from a PDF attachment of a Zotero item.' It clearly distinguishes this tool from siblings like zotero_get_item_fulltext by emphasizing page-specific reading and by referencing zotero_get_pdf_outline as the precursor. The two output formats are also stated, so an agent can tell exactly what this tool is for.

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 'Use this when you know which pages to read — for example after getting the PDF outline via zotero_get_pdf_outline.' That gives clear context for when to invoke it and points to a related sibling tool. It does not explicitly name alternatives to avoid, such as full-text extraction, so it stops short of a full when-not list.

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