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

Well beyond the annotations (readOnly/idempotent/destructive/openWorld), it discloses failure transport (422 for image-only), the 100K char cap, the charging model (fails are not charged, $0.02 via x402/USDC on Base), and a security warning that returned content is untrusted. This is unusually rich behavioral context for a read tool.

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?

It is front-loaded with the core purpose and every sentence carries information (constraints, return shape, billing, safety). The single dense paragraph is efficient, though the packing of pricing and metadata fields makes it slightly heavy to scan.

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?

With no output schema, the description fully specifies the return payload (pages, totalPages, pagesReturned, truncated, bytes, finalUrl, meta), coverage limits, error behavior, and billing, so an agent has everything needed to call and interpret the tool correctly.

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%, so both parameters (url, pages) are already documented with their constraints. The description restates the same facts (http/https, max 10MB, pages 1-50, default 50) without adding format or syntax detail beyond the schema, so the baseline 3 applies.

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 opens with a precise verb+resource ('PDF to text') and scopes it to 'the text of a public PDF' via GET. This clearly distinguishes it from generic siblings like fetch, http, and extract, letting an agent route PDF-extraction tasks here without opening a schema.

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?

It gives strong implied usage context ('public PDF', http/https, max 10MB, no OCR so image-only PDFs get 422), which tells the agent when the tool will and won't work. However, it never names an alternative sibling (e.g., fetch or extract) or explicitly states when to prefer this tool over them, leaving sibling selection to inference.

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