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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description adds substantial context on top: the 0.02 USDC per-call cost with the x402 payment chains, the 20,000-token truncation cutoff plus how much was read, and that output is grounded strictly in the document. These are the exact behavioral facts an agent cannot get from structured fields.

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-loads the usage trigger and keeps the return/truncation facts tight. The cost sentence is the weakest part, enumerating five chains, but it is genuinely useful information rather than filler, so it mostly 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?

An output schema exists, so return shape need not be spelled out, yet the description still covers the practical concerns: cost and payment rails, truncation at 20,000 tokens with the read amount, and grounded-only output. Nothing an agent needs to invoke this correctly is missing.

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 coverage is 100%, so url and the length enum are already fully documented in the schema. The description's 'short or medium summary with key points' only loosely restates the length parameter without adding format or word-count detail beyond the schema's own '(about 60 words) or medium (about 150)'. Baseline 3 is appropriate.

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?

States a specific verb and resource: it produces a short/medium summary of a web page or PDF, with key points. That clearly separates it from raw-extraction siblings like get_pdf_markdown or get_extract, though no sibling is named explicitly, so it stops short of a 5.

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 opening 'Use when an agent needs the gist of a web page or PDF' gives an explicit trigger condition. It does not, however, state when NOT to use it or point to the overlapping alternatives (get_extract, get_pdf_markdown, get_web_markdown), which leaves routing among near-neighbors partly to inference.

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