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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real behavioral context beyond them: robots.txt compliance, a no-retention/no-redistribution policy, and a cost of $0.0005 via x402. Cost and legal constraints are exactly the kind of traits an agent can't get from the annotation block, though failure/rate-limit behavior is still unstated.

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?

Three short, front-loaded sentences: what it does, what it returns, then the legal and cost caveats. No filler and each sentence carries distinct 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 discloses the return format ('clean Markdown'), and it covers cost, compliance, and retention. For a single-parameter read tool with supporting annotations, nothing essential to correct invocation 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?

There is a single url parameter with 100% schema description coverage ('Public http(s) URL'), so the schema already carries the meaning. The description's 'public' reinforces the constraint but adds no syntax or format detail, making the baseline 3 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?

The description gives a specific verb+resource: it fetches a live public web page and returns clean Markdown. The scope word 'live' and 'public' help distinguish it from archive-oriented siblings, but it never explicitly names or contrasts with get_document, get_fulltext, or search_archive, so an agent must infer the boundary itself.

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 implies when to use it (fetching a live public page) and states two preconditions ('public', 'robots.txt respected'), but offers no explicit when-not guidance or named alternatives among the siblings. Usage is inferable rather than stated.

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