pdf_reader

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

No annotations are provided, so the description must fully disclose behavior. It mentions the output (text per page) but omits limitations such as lack of OCR for scanned PDFs, potential output formatting details, or performance characteristics. This is a notable gap for an AI agent deciding whether the tool suits a task.

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 two short sentences, front-loaded with the action and output. Every word earns its place, with no redundant or vague filler.

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?

The description covers the core behavior and return value, but since there is no output schema, it leaves ambiguity about the return format (e.g., string vs list, page delimiters). Additionally, it does not address limits like scanned PDFs or large files, making it adequate but not 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 schema description coverage is 100% for the single parameter (file), so the baseline is 3. The description adds no additional semantic meaning beyond what the schema already provides, which is acceptable given full coverage.

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') and resource ('PDF'), and clarifies the scope ('all text content', 'text of each page'). This clearly differentiates it from siblings like get_page_text, which likely targets specific pages.

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 implicitly indicates when to use this tool (when all PDF text is needed), but it does not explicitly mention alternatives or excluded scenarios. Given the many sibling PDF tools, there is no guidance on preferring get_page_text or pdf_search for partial extraction.

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