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

The description goes well beyond the readOnlyHint annotations by revealing important behavior: it handles compressed streams, PDF 1.5+ object streams, and ToUnicode CMaps, and honestly reports encrypted or image-only documents instead of returning garbage. It also discloses the cost and payment protocol, which is material side-effect information.

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?

Three focused sentences: core function, technical robustness and honesty guarantees, and cost/payment. Every sentence earns its place, and the most important usage information is front-loaded.

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 a rich output schema, 100% parameter coverage, and annotations covering read-only/idempotent behavior, the description fills the remaining gaps: failure honesty, format support, and cost. An agent has everything needed to select and invoke 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%, with both url and max_pages already documented. The description adds no additional parameter-level meaning beyond 'by URL,' so the baseline of 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 specific verb and resource: 'Extract text from a PDF by URL.' It clearly defines what the tool does and is immediately distinguishable from siblings like scrape or compress.

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?

The description gives clear context for when to use the tool: whenever text extraction from a PDF at a URL is needed. It does not explicitly name alternatives or exclusions, but the purpose is specific enough that an agent can route to it confidently.

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