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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: no JavaScript is executed and the returned surface is status/title/text/links. That tells the agent the result is the raw delivered HTML-derived content, which is the key operational caveat. The opaque phrase "Works on every key" adds no usable information.

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 compact sentences, front-loaded with what is returned and the no-JS constraint, followed by the escape hatch to `see`. The sentence "Works on every key" is filler with no discernible meaning for an agent and slightly muddies an otherwise disciplined description.

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 carries the burden of describing the return shape (status, title, text, links) and the silent limitation (no JS execution). The main remaining gap is the dangling `sparse` reference, which an agent cannot resolve from this definition alone.

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?

There is a single parameter, `target`, and schema coverage is 100% – it is already documented as an http(s) URL. The description adds no additional meaning (no format examples, no redirect/timeout behavior, no notes on what happens with non-HTML targets), so this sits at the high-coverage baseline.

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 (a URL), and enumerates exactly what comes back: status, title, text and links. It also carves out a clear boundary against the sibling `see` tool, so an agent can discriminate `read` from `see` without opening either schema.

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 an explicit alternative and the condition that selects it ("If `sparse` is true ... use `see` instead"), which is exactly the routing guidance an agent needs. It loses a point because `sparse` is not a declared parameter of this tool, so the agent has to infer whether that is a return field or something from another tool before the condition is actionable.

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