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

With only readOnlyHint and openWorldHint given, the description adds substantive behavior: 6 credits per successful call, schema-invalid input rejected before billing, and the fact that results contain one entry per page the provider could actually read (i.e., partial failures do not abort the call). That billing and partial-success disclosure is exactly the context an agent needs to avoid surprise cost and misread results.

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 sentences, front-loaded with the capability and scope, then the return shape, then cost. No filler and nothing repeated from the schema verbatim.

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?

There is no output schema, and the description compensates by spelling out the exact result object shape (url, title, publishedDate, text, characters) and per-page granularity. Together with cost and input rejection rules, an agent has everything needed to call it and interpret results.

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%, so the schema already documents the URLs array (1–5, public http(s) only) and maxCharacters (500–10,000). The description echoes those caps but adds no new syntax or format detail beyond them, so the 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?

States a specific resource (public web pages) and output (clean text), plus a concrete scope limit of 5 pages. It does not differentiate from the crowded set of web siblings (web-scrape, web-extract, page-markdown, web-map), so an agent cannot tell from this text alone which to pick.

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?

'For agents to read' implies a read/extraction use case, and the 5-URL cap implies batch reading, but there is no explicit when-to-use, when-not, or named alternative among the many web tools. An agent must infer selection from the sibling list rather than the description.

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