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

With no annotations, the description carries the full burden. It discloses important limitations (no JavaScript execution, won't work with paywalled/login-protected/SPA pages) and describes the transformation (stripping HTML/boilerplate). It omits error/status behavior, but this is a read-only fetch tool and the disclosures are substantial.

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?

The description is a single well-organized paragraph: primary function, outputs, usage rationale, alternatives, and limitations. Every sentence adds value, and the core purpose 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?

With no output schema and no annotations, the description compensates by listing return fields (title, meta description, word count, body text) and highlighting limitations. It gives an agent enough context to select and invoke the tool correctly, even covering integration with web_news_headlines.

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%, with detailed descriptions for each parameter including defaults and constraints. The tool description itself does not add parameter-level meaning beyond the schema, so baseline 3 is 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 uses a specific verb ('fetches') and resource ('public web page'), explicitly lists outputs (title, meta description, word count, main body text), and differentiates from sibling 'web_news_headlines' by cautioning not to use it for headline discovery. This clearly distinguishes it from siblings.

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?

Provides explicit when-to-use ('when an agent needs to read the content of a specific web page or article URL'), concrete examples, and an explicit when-not-to-use ('Do not use this tool to discover current news headlines — use web_news_headlines instead'). It even instructs to pass article URLs from web_news_headlines to this tool.

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