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

The annotations already mark it read-only, idempotent, and non-destructive. The description adds useful behavioral details: it returns clean text plus metadata, it costs twice as much as a web search per URL, and it accepts up to 100 URLs per call. These details go beyond the annotations and do not contradict them.

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 sentences deliver purpose, usage timing, cost, and capacity with no filler. The most important 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?

For a simple read-only tool with two parameters and no output schema, the description is mostly complete: it covers what it returns, when to use it, cost, and URL limit. The only clear gap is the undocumented markdown parameter.

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?

With 0% schema description coverage, the description carries the parameter-documentation burden. It explains that the urls array accepts up to 100 URLs per call, but it does not explain the optional markdown boolean or what it changes about the output.

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 clearly states that the tool reads a web page and returns clean text plus metadata, which is a specific verb and resource. It also distinguishes itself from the busca_google_* search siblings by saying it is used after a search to open interesting links.

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 gives explicit usage context: use after a search, for opening links that interested. It does not explicitly name a when-not-to-use alternative, but the sibling search tools are clearly the alternative for actual search queries.

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