read_pdf_pages

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

Annotations already establish that this is read-only, idempotent, and non-destructive, so the bar for extra disclosure is lower. The description adds value beyond annotations by disclosing the cost profile ('cheapest'), the plain-text output, and the lack of Markdown table reconstruction, which shapes caller expectations.

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 short sentences front-load the action and then pack the use case, return format, and the one critical constraint ('pages' is required) without redundancy. Every sentence earns its place.

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 focused read operation with a rich output schema and safety annotations, the description covers what the tool does, when to call it, what output to expect, and the key requirement. Nothing needed to invoke it correctly is missing at this level of complexity.

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 url, pages, filename, password, and file_base64. The description reinforces that 'pages' is required, but adds little semantic detail beyond that; note the top-level schema lists no required parameters, so the description is the only signal of pages being mandatory.

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 the plain text of specific PDF pages') and scopes it to a known location in a large PDF. It also distinguishes the output from Markdown reconstruction and references the sibling flow (search_document/get_document_info), so an agent can identify what this tool does at a glance.

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?

It gives a concrete when-to-use context: after search_document or get_document_info has located page numbers, and frames this tool as the cheapest way to inspect a known location. It does not explicitly name alternative tools for markdown/table conversion or state when not to use it, so it stops short of a full exclusion rule.

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