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

Annotations only cover readOnlyHint and openWorldHint; the description adds the costly details an agent cannot get elsewhere: the 25 MB / 300-page ceiling, refusal of text-layer-less PDFs at no charge, $0.005 USDC pricing under x402, failed calls being free, and the three-free-calls-per-day quota. The quote-then-sign payment handshake is also spelled out, so no annotation contradiction exists.

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?

Front-loaded with the core action, then cleanly sectioned into pricing, 'When to use', 'Use instead', 'Parameters', and 'Returns'. It runs long for a three-parameter tool and repeats the 'scanned PDFs without a text layer are refused at no charge' clause in both the intro and the Returns section, which is the only wasted text.

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?

There is no output schema, so the description correctly enumerates the return shape (title, author, page_count, pages_read, ordered pages[] of text). Combined with the stated size/page limits, refusal behavior, and the x402 payment/quota mechanics, an agent has everything needed to call this correctly on the first attempt.

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 a baseline of 3 is warranted, but the description adds useful framing: url must be an absolute http(s) PDF link, max_pages is bounded 1–300 with a default of 50, and the payment parameter's workflow (omit it for a quote, sign and call again) is explained in prose rather than left to the field blurb.

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?

Opens with a concrete verb+resource ('Read a PDF from a URL as text, page by page') and enumerates what comes back (title, author, page count). It explicitly distinguishes itself from the closest sibling by naming read_page for ordinary web pages, so an agent can pick correctly 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?

Contains an explicit 'When to use' condition (the link is a PDF — filing, paper, contract, manual) and an explicit 'Use instead' alternative (read_page for ordinary web pages). The limits section also tells the agent when the tool will refuse (scanned PDFs, >25 MB, >300 pages), which is actionable routing information.

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