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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false; the description adds meaningful behavioral context beyond them. It discloses HTML-only scope, LLM processing, navigation/boilerplate stripping, pricing at $0.01/call, failed calls being free, and that repeated calls are charged. These are exactly the operational details an agent needs before invoking it.

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 front-loaded with the core behavior and keeps alternatives, cost, and example close at hand. It is somewhat dense with pricing and operational notes, but nearly every sentence contributes useful context for invocation. Minor redundancy exists in restating the read-only nature already covered by annotations.

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 one-parameter tool with no output schema, the description is complete: it defines the output shape (short summary plus key points), scope (HTML only), alternatives for PDFs and full text, cost model, and an example. Nothing essential for correct invocation appears missing.

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 coverage is 100% and the single url parameter is already documented as an absolute http(s) URL. The description adds value with an example URL and the important constraint that only HTML pages are handled, pointing PDFs elsewhere. This goes beyond the schema, though it does not add more URL formatting rules.

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 gives a specific verb and resource: fetch a web page and summarize it into a short summary plus three to six key points. It distinguishes itself from siblings by naming pdf_text and extract as alternatives for PDFs and full text. An agent can identify exactly what this tool produces without opening the schema.

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 states clear use cases: research, news triage, link previews, and deciding whether a page is worth reading. It also explicitly routes agents elsewhere for PDFs (pdf_text, then ai_summarize_text) and full text (extract). This is explicit when-to-use and when-to-use-alternatives guidance.

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