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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds genuine behavioral context beyond them: it discloses the rendering mechanism, the return format (readability markdown), that it is free, and that the default mode declares identity. It still omits failure/rate-limit behavior and the meaning of the tier-gated params, keeping it short of a 5.

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?

Two tightly packed sentences that front-load the core value proposition (JS rendering that fetch can't do) and trail the cost and identity notes. No filler; every clause 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 correctly states the return shape (clean readability markdown). It also notes it is free and mentions identity declaration. It falls short of fully covering the tier/handle/account gating implied by the schema, but is otherwise sufficient for calling the 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 description coverage is 100%, so the schema already documents url, mode, handle, and account, giving a baseline of 3. The description adds only marginal meaning — "the default mode declares identity" loosely ties to mode=enums["honest"] — and says nothing about how handle/account alter behavior beyond what the schema already states.

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), resource (a web page), and a concrete differentiator: it renders the real JavaScript/SPA page in a headless browser and returns clean readability markdown. The contrast is drawn against `fetch`, though not against the sibling `browse_read`, which sounds functionally adjacent — so it is clear but leaves sibling differentiation to inference.

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 phrase "the way `fetch` can't" implies usage (reach for this when a plain fetch won't render the page), and "Free" hints at a cost consideration. But no sibling is named and there is no explicit when-not guidance versus `browse_read`, `browse`, or `web_search`.

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