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

Annotations already mark read-only/idempotent/non-destructive, and the description adds meaningful behavioral constraints beyond them: it is bounded to at most five pages, executes no JavaScript, sends no cookies/credentials, and cannot reach private networks. These are exactly the auth and limit details that matter for safe invocation.

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 sentences with no filler: the first states operation and outputs, the second states constraints and exclusions. Key scoping information is front-loaded.

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?

There is no output schema, so listing the returned categories is essential and done. The description covers inputs, bounds, and safety constraints. The only notable gap is a minor ambiguity in whether 'up to four linked pages' is always the behavior or whether max_pages controls the total count including the seed page.

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 baseline applies. The description reinforces that the URL must be public and that the pages are same-origin linked pages, but it does not add materially new parameter-level syntax or format details beyond the schema.

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 specifies a concrete verb ('Read'), a bounded target (a public seed page plus up to four same-origin linked pages), and the exact return payload (compact readable text, headings, links, source hashes, evidence receipts). It is distinct from the sibling fetch tools because it defines a bounded site-research behavior rather than generic fetching.

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 clearly states the applicable context: public websites, browserless, no JavaScript, no cookies/credentials, no private networks. This implicitly tells an agent not to use it for authenticated, dynamic, or internal sites, but it does not name an explicit alternative tool or when to prefer one sibling over another.

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