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

Annotations cover the safety profile (readOnly/openWorld/idempotent), and the description adds substantial context beyond them: robots.txt compliance, a per-call price of $0.02 USDC via x402, no interaction support, and proof-of-exit-IP metadata. Cost and payment protocol disclosure is exactly the kind of operational detail an agent needs before invoking.

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 and scope are front-loaded, then returns, then use case, then constraints, then price — a logical order with no filler. It is dense as a single block but every sentence carries information.

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 no output schema, the description fully enumerates the return payload, and for a paid, open-world fetch tool it discloses cost, payment mechanism, robots.txt behavior, and interaction limits. Nothing an agent needs to decide or call 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 description coverage is 83% and each parameter (url, country, device, waitMs, waitUntil, include.*) is already documented in-schema. The description only loosely reinforces that the country is user-chosen and that HTML/screenshot are optional, adding little beyond the schema — the baseline 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?

States a specific verb and resource ('Loads a public web page in a real Chromium browser') plus the distinguishing scope: JavaScript executed, residential IP, user-selected country. It also enumerates what comes back (visible text, title, final URL, HTTP status, optional HTML/screenshot, exit IP proof), so an agent knows exactly what it gets.

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 a concrete use case ('see prices, content or availability as a visitor in that country sees them') and hard capability boundaries ('no clicks, logins or CAPTCHA solving'). It doesn't point to a sibling alternative, but no sibling in this toolset is a comparable render/fetch tool, so the gap is minor.

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