parse_pdf_to_text

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds valuable behavioral context: not suitable for scanned PDFs without embedded text, with specific output format ('(no extractable text)') for such pages.

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?

Four sentences, each adding value: action, use case with combination, warning about alternatives, and limitation. No wasted words. Well-structured with front-loaded purpose.

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 that an output schema exists (context indicates true), the description explains return behavior (page-by-page, placeholder for non-text pages). Covers prerequisites, use cases, and limitations. Complete for a single-parameter tool with good annotations.

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?

Only one parameter (pdf_url) with schema description 'Direct HTTPS URL to the PDF file'. Schema coverage is 100%, so description does not need to add much. Description does not repeat schema details, but it is acceptable.

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?

Clear verb (download and extract text), resource (PDF from URL), and scope (page by page). Distinguishes from sibling search_filings by stating it's for full text of a specific document.

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?

Explicitly states when to use (after search_filings for full text) and when not to use (if PDF is well-represented in database or is scanned). Names alternative (search_filings) and highlights speed advantage.

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