pdf_read_text

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

No annotations are provided, so the description carries full burden. It discloses that only text-based PDFs are supported (not scanned images) and that extraction can be from all or specific pages. This is good behavioral context for a read-only operation, though it doesn't mention return format or error handling.

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 extremely concise at two sentences with zero wasted words. The main purpose is stated first, and limitations are immediately provided. 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?

Given the tool has no output schema and only two parameters, the description covers the core functionality well. However, it does not mention what the output looks like (e.g., plain text string, object with page numbers), which would be useful for an agent to know what to expect.

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% (both parameters described). The description adds value by clarifying that pages are 1-indexed and that omitting the pages parameter extracts all pages. This goes beyond the schema's basic descriptions.

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 uses a specific verb 'Extract text content' and clearly identifies the resource 'PDF file'. It distinguishes itself from sibling tools by specifying it handles text-based PDFs (not scanned), which is unique among the many PDF tools listed.

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 implies usage for text extraction but does not explicitly state when to use this tool versus alternatives like pdf_search (which likely searches for text) or pdf_form_read. No guidance on when not to use it or prerequisites is provided.

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