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 the full burden. It discloses key behaviors: pages are 1-indexed (though the schema also states this) and the return format is Markdown with heading structure preserved. It does not mention error handling or side effects, but for a read-only operation with clear output description, this is sufficient. It adds value beyond the schema by describing the output structure.

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?

Two sentences with no filler. The first sentence states the action and usage condition; the second adds indexing and output format. It is front-loaded and every sentence carries meaningful information, making it highly efficient.

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 simple tool with 3 parameters, full schema coverage, and an output schema present, the description covers all essential aspects: what it does, when to use it, indexing, and return format. It is complete for an agent to decide when to call it and to interpret the response. No critical gaps remain.

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 baseline is 3. The description does not add new parameter-specific details beyond what the schema already provides (e.g., 1-indexing, optional end_page). However, it does add context on when to use the tool, which is useful but not directly about parameter semantics. It adequately meets the baseline without further elaboration.

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 states a specific action ('Read specific page range(s)') on a clear resource ('PDF attachment of a Zotero item'), and explicitly ties usage to knowing which pages to read, referencing the sibling tool zotero_get_pdf_outline for context. This distinguishes it from related tools like zotero_get_pdf_outline and zotero_get_item_fulltext without ambiguity.

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 when you know which pages to read — for example after getting the PDF outline via zotero_get_pdf_outline.' This tells the agent when to invoke it and implies the complementary tool to use beforehand, effectively routing to the correct sibling.

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