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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real extra context beyond that: a cost signal ('cheap and precise'), the batch limit of four pages, Markdown output, and pagination behavior.

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 tight sentences, front-loaded with the capacity limit and then the two execution modes. No filler; the mode fork is presented cleanly. Slightly dense but nothing wasted.

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?

An output schema exists so return values needn't be re-explained, and the description correctly covers the essentials. Still, it omits any alternative-tool routing and says nothing about the 'live' flag or failure behavior, which leaves gaps for a multi-page fetch 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 0%, so the description must carry the parameter burden. It explains 'context' (focused question, cheap/precise) and hints at 'start' via pagination, but says nothing about 'live' or the 'url' field, leaving meaningful schema gaps unfilled.

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 ('Open up to four public pages') and adds scope detail (public, max four). It does not, however, distinguish this from the obvious sibling search_web, so an agent must still infer which one it wants.

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 description gives useful internal mode guidance ('Pass a focused context... or omit it to read the full page'), but that is mode selection, not tool selection. It never says when to prefer this over search_web or any other sibling, so alternative routing is left entirely to inference.

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