read_pdf_page

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

No annotations are provided, so the description carries full burden. It states the action 'read' but doesn't disclose behavioral traits like permissions needed, file size limits, rate limits, output format (e.g., text, images), error handling, or whether it's read-only/destructive. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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?

The description is a single, efficient sentence with zero waste. It's front-loaded with the core action and resource, appropriately sized for the tool's complexity. Every word earns its place without redundancy.

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?

Given no annotations, no output schema, and 4 parameters with full schema coverage, the description is minimally adequate. It covers the basic purpose but lacks details on behavior, output, or usage context. For a read operation with no structured safety hints, it should do more to explain what 'read' entails and potential limitations.

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 fully documents all 4 parameters (path, page, startPage, endPage). The description adds minimal value beyond the schema, mentioning 'page or range of pages' which aligns with parameters but doesn't provide additional syntax, constraints, or examples. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the verb 'read' and the resource 'PDF file', specifying it's for 'a specific page or range of pages'. It distinguishes from sibling 'read_pdf' (likely reads entire PDF) and 'get_pdf_metadata' (metadata-focused), but doesn't explicitly mention 'search_pdf' (search-focused). The purpose is specific but could be more precise about sibling differentiation.

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?

No guidance on when to use this tool versus alternatives like 'read_pdf' (full PDF) or 'search_pdf' (content search). The description implies usage for partial reading but doesn't specify scenarios, prerequisites, or exclusions. It lacks explicit when/when-not instructions or named alternatives.

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