read_pages

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

No annotations are provided, so the description carries the behavioral burden. It discloses automatic OCR handling for scans/garbled pages, the needs_ocr sentinel, and the fallback options. It stops short of confirming read-only/no-side-effects behavior or error handling for invalid volumes/ranges, but the main behavioral surprises are covered.

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?

Every sentence carries operational value: main action, OCR behavior, explicit fallback condition, citation rule, and a clear parameter block. The structure is dense but well-organized and not padded.

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 read tool with no annotations, this covers purpose, OCR behavior, fallback routing, citation requirements, and parameter constraints; the presence of an output schema covers return-format details. The missing case_id mention and lack of invalid-input/error behavior keep it from being 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 description adds rich meaning to volme, start_page, and end_page: requiredness, 1-based inclusive semantics, and where valid volume names come from. However, it omits the top-level required case_id that appears in the input schema, and the schema's args is free-form, so the exact mapping between description and invocation structure is not fully seamless.

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?

States a specific verb and resource: read a page-range from a named volume, with each page labeled by page number. It also differentiates from get_page_image by framing that tool as the OCR-failure fallback, and from list_volumes/search_volumes as the source and search prequels.

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?

Explicitly says when to use read_pages (whenever text from a volume page range is needed) and when not to: only switch to get_page_image when a page still shows needs_ocr. It also references list_volumes for valid volume names and gives a required citation format.

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