read_pdf_page

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

With no annotations, the description carries the full burden, and it does add real context: page numbering is 1-based and the returned data includes a SHA-256 document fingerprint. It omits what happens on pages without selectable text (e.g., scanned PDFs) and gives no error or pagination behavior, leaving notable gaps.

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?

A single tight sentence with no padding, front-loading the core action. Efficient, though the fingerprint tail could arguably be trimmed since there is no output schema to explain return values.

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 two-parameter read tool with no output schema, the description covers the essentials (text extraction, 1-based indexing, fingerprint). It still lacks file-format guidance and scanned-PDF limitations that an agent would need to call it correctly.

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 0%, so the description must compensate. It clarifies that 'page' is 1-based, which is genuinely useful, but says nothing about the required 'file' parameter (path vs. id, accepted formats), so half the parameters remain unexplained.

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 ('Read') and resource ('selectable text from a 1-based PDF page'), which distinguishes it from the rendering sibling by emphasizing text extraction rather than image output. However, it never names render_pdf_page or any alternative, so the distinction is only implicit.

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?

There is no explicit when-to-use or when-not-to-use guidance. The phrase 'selectable text' hints that image-only/scanned pages are out of scope, but the agent is left to infer this and gets no routing help against render_pdf_page.

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