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

Beyond the annotations, it discloses concrete limits (10 MB, up to 200 pages), output capping via maxChars, the exact failure modes that produce errors, and the crucial detail that these failures are 'uncharged.' It also spells out the paid-call mechanics ($0.005 USDC on Base via x402), which explains why readOnlyHint is false despite the read-like framing.

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 front-loaded with purpose and returns, then layers limits, failure modes, use case and pricing in a logical order where each sentence carries distinct information. It is somewhat clause-dense but not padded, so nearly every sentence earns its place.

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 carries the return-value burden, naming the returned text and metadata (title, author, page count, character counts). Combined with size/page limits, charging rules and failure conditions, an agent has everything needed to invoke it 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 the schema already documents url, pages, maxChars and firstPage with ranges and defaults, making 3 the baseline. The description adds only light reinforcement ('choose a first page and how many pages to read', 'cap the output with maxChars') and no syntax or interaction detail 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 pairs a specific verb and resource ('Download a public PDF ... and return its text page by page') with concrete scope (public, up to 10 MB) and enumerates the returned fields. It is unambiguous about what the tool does, though it never names a sibling (e.g., text_extract or html_to-text) to disambiguate format handling.

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 states the intended context explicitly ('Use to read papers, invoices, reports and manuals into an agent's context') and lists failure conditions (scanned PDFs without a text layer, encrypted files, non-PDF URLs). It stops short of naming an alternative tool for cases that fall outside PDF handling, so it lacks exclusions.

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