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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses the one-call extraction behavior, returned artifacts (page count, likely_scanned flag), the no-OCR limitation, billing side effect, and the free-on-failure policy. This is unusually transparent for a tool definition.

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 compact and front-loaded with the core purpose, followed by constraints, pricing, and failure policy. Every sentence adds useful information, and there is no wasted wording or repetition of schema details.

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 single-parameter tool with no output schema, the description is remarkably complete. It specifies input requirements, size limits, output highlights (page count, likely_scanned flag), OCR limitation, cost, and failure semantics. An agent has everything needed to decide whether and how to call this tool.

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 input schema already documents the lone 'url' parameter as 'public http(s) URL of a PDF file,' giving 100% coverage. The description reinforces that the URL must be public and that the file is a PDF, but adds no fundamentally new parameter-level syntax or format details beyond the 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 states exactly what the tool does with a specific verb and resource: 'Convert a public PDF to plain text.' It also disambiguates itself by explicitly limiting to text-based PDFs and noting 'no OCR,' which distinguishes it from scanned-PDF tools and related text-processing siblings.

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?

Usage conditions are made explicit: the PDF must be public, under 25MB/500k chars, and text-based rather than scanned. It also explains pricing and how to obtain credentials, giving clear context for when the tool is appropriate, though it doesn't explicitly name alternative tools for other PDF scenarios.

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