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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses the fetch → Kitesurf → Chromium escalation ladder, that the chosen engine is reported back, that requests are refused free of charge on robots.txt or bot-check, and the exact $0.004 success-only price. These are the operational facts an agent needs before committing a paid call.

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 return value, then engine strategy, then refusal rules, then cost — a sensible order. Four dense sentences, each doing work; only the price clause is mildly redundant with 'charged only on success'.

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?

No output schema, yet the description specifies the return format (Markdown, absolute links) and which engine succeeded. It is missing truncation behavior for max_chars and any mention of error shapes, but for a single-URL fetch with annotations covering safety, coverage is good.

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 0% for four parameters, so the schema carries no semantics. The description explains the escalation behavior that underlies the 'engine' enum ('auto' means try cheapest first), which is genuinely useful, but says nothing about max_chars truncation or user_agent overrides.

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 outcome: returns the main content of a web page as clean Markdown with absolute links. That is clearly distinct from screenshot (image capture) or extract (structured data) among the siblings, though no sibling is named explicitly.

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 describes conditions under which the tool refuses (robots.txt, Content Signals, bot check) and that billing only applies on success, which implicitly frames when it is appropriate. But it never names an alternative like extract, preflight, or screenshot, nor says when to prefer them.

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