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

Annotations already flag openWorldHint and non-idempotent, and the description adds substantial context beyond them: a full SSRF fence, refusals billed at $0 which happen before payment, no caller cookies/credentials accepted, per-leg pricing, and the exact x402 payment retry flow over MCP. That is unusually rich behavioral disclosure.

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 core action is front-loaded, but the paragraph is a dense run-on that repeats pricing ($0.02 appears twice) and packs payment, preflight, SSRF, and sibling-equivalent info without structure. Informative but not tight.

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?

For a paid, open-world render tool with no output schema, the description covers output shape (inline base64 PNG plus text/markdown with counts), pricing per leg, payment mechanics, SSRF safety, and a free preflight path. Nothing essential to a correct call 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?

With 100% schema coverage the baseline is 3, but the description adds real meaning: it shows the body shape, ties op to leg pricing and to height being rejected on full-page, and notes max_chars truncation disclosure. The overlap with the schema's own op/height text keeps it from a 5.

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 states a specific compound action: render a public web page with headless Chromium and extract text/markdown from the same session, with PNG output. That is far more specific than the name alone. It does not explicitly name siblings like screenshot_render or access_crawl, so differentiation is inferred from the bundle/extraction framing rather than stated.

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 clearly explains how to pick a leg (bundle vs full-page vs read) via the op field and what each costs, which is genuine usage guidance. However, it never says when to choose this tool over the many sibling render/crawl/screenshot tools, nor any exclusion beyond 'one public web page'.

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