zotero_read_pdf_pages

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

No annotations are provided, so the description carries full behavioral burden. It discloses that pages are 1-indexed, that reading specific pages is the behavior, and that it 'Returns Markdown with the page's heading structure preserved' — which adds meaningful behavioral detail about the output format beyond the output schema. Solid disclosure for a read operation without annotations.

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 concise sentences, zero filler. Each sentence earns its place: purpose, usage context, and indexing convention. Front-loaded with the core action and resource.

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?

The tool has an output schema that documents the Markdown return, so explaining return values isn't the description's job. Given complexity is moderate (3 params) and schema coverage is 100%, the description provides the key workflow context (use after outline, page indexing) that completes the picture. Missing explicit exclusion scenarios, but otherwise comprehensive for this read-only tool.

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 description coverage is 100%, so the schema already documents all parameters. The description adds the page-indexing convention (1-indexed) and clarifies the end_page default behavior the schema already states ('If omitted, reads only start_page'). It adds the workflow context linking to the outline tool, but mostly relies on the schema for parameter meaning. Baseline 3 is appropriate.

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?

Specific verb+resource: 'Read specific page range(s) from a PDF attachment of a Zotero item.' Clearly states the action (read pages) and the resource (PDF attachment). Distinguishes from siblings like zotero_get_pdf_outline (which gets the outline) and zotero_get_item_fulltext (which gets entire text), by emphasizing page-range targeting.

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?

Gives clear context for when to use: 'Use this when you know which pages to read — for example after getting the PDF outline via zotero_get_pdf_outline.' This implies the alternative workflow (get outline first) and sets expectations about the prerequisite knowledge. However, it doesn't explicitly say when NOT to use it, though the sibling distinction is implied.

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