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

No annotations are provided, so the description carries full burden of behavioral disclosure. It discloses that the tool does not execute JavaScript, will not work with paywalled, login-protected, or JavaScript-rendered single-page applications, and describes the return format (title, meta description, word count, body text). This is comprehensive for a read-only public web fetcher.

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 moderately long but every sentence contributes useful information—purpose, output, usage examples, exclusions, and limitations. It is front-loaded with the core function and progressively adds context, maintaining focus without clutter. Slightly verbose but efficient.

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?

Given the tool's simple structure (3 parameters, no output schema), the description adequately explains the input, output, and limitations. It provides examples of appropriate URLs, mentions truncation behavior, and clarifies the non-JavaScript constraint, making it self-sufficient for an agent to use correctly. No major gaps remain.

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?

The input schema already covers 100% of parameters with descriptions, so the description does not need to re-explain them. However, it adds valuable context beyond the schema: max_chars defaults to 8000 with a range up to 50000 and indicates whether content was truncated, and include_links defaults to false with a use case for crawling. This complements the schema effectively, though it doesn't fully replace the need for the schema's own descriptions.

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 it fetches any public web page and returns clean, readable plain text stripped of HTML, navigation, scripts, advertisements, and boilerplate. It specifies the output (page title, meta description, word count, main body text) and explicitly distinguishes itself from web_news_headlines, making its purpose and scope unambiguous.

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?

Explicitly states when to use the tool (summarizing an article, extracting facts, verifying claims, converting a web page to plain text) and when not to (discovering current news headlines, which is web_news_headlines's job). It also gives a concrete example of passing article URLs from web_news_headlines, and notes limitations with JavaScript-rendered or paywalled pages, providing clear guidance for an agent.

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