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

Although annotations already cover read-only, open-world, idempotent, and non-destructive behavior, the description adds substantial context: robots.txt enforcement per user agent, risky-site content marking, refund if nothing can be read, per-call pricing, and return fields including preflight and screenshot. There is no contradiction with annotations.

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 purpose and includes a structured Returns list. The pricing, free sample, and exhaustive return fields are useful but make it denser than strictly necessary; still, there is little 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?

No output schema exists, so the description carries the return-value burden and does so by listing the main fields and embedded preflight/screenshot objects. With annotations already covering safety and idempotency, this is complete enough for a three-parameter read tool.

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 the schema already documents url, ua, and screenshot. The description adds only high-level mentions of screenshot-on-request and preflight verdict, not syntax or meaning beyond the schema, so the 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 ('Read') and resource ('web page') and says what it produces: clean markdown plus a preflight verdict and optional screenshot. This is specific enough to distinguish it from siblings like url_preflight and site_screenshot, even though alternatives are not explicitly named.

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?

Gives useful behavioral context such as robots.txt handling, untrusted-content flagging, refunds, and price, but does not explicitly say when to use this instead of url_preflight or site_screenshot. Usage is implied by 'read a web page' rather than by routing guidance.

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