extract_text_from_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes what the tool does (extracts text) and what it doesn't do (no Markdown conversion), but lacks information about error conditions, performance characteristics, or file format limitations. It provides basic behavioral context but misses important operational details.

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 well-structured with clear sections (purpose statement, Args, Returns) and efficiently communicates essential information. The single-sentence purpose statement is front-loaded, though the parameter documentation section is somewhat lengthy but necessary given the schema coverage gap.

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 3-parameter tool with no annotations and no output schema, the description provides good parameter documentation and clear purpose, but lacks information about return format details, error handling, or performance considerations. It's adequate for basic usage but incomplete for robust agent operation.

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?

With 0% schema description coverage, the description fully compensates by providing detailed parameter documentation in the Args section. Each parameter is clearly explained with examples for 'page_numbers', including format specifications like 'all', comma-separated numbers, and ranges. This adds substantial value beyond the bare schema.

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 'extract' and resource 'text content from a PDF file', distinguishing it from sibling tools like 'convert_pdf_to_markdown' by specifying 'without conversion to Markdown'. This provides specific differentiation from similar tools.

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 suggests usage context by contrasting with conversion tools ('without conversion to Markdown'), but doesn't explicitly state when to use this tool versus alternatives like 'get_pdf_info' or 'convert_pdf_to_markdown'. It provides clear purpose but lacks explicit when/when-not guidance.

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