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

With readOnlyHint and openWorldHint already covering the safety profile, the description adds genuinely useful behavior: a per-call cost of $0.02 USDC via x402, and the partial-failure semantic that unreadable pages are flagged rather than failed. It does not disclose return shape or async execution behavior, but the cost and failure-handling disclosures go well beyond the annotations.

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 tightly packed sentences with the core purpose ('Bulk reader') front-loaded, followed by scope, failure semantics, and cost. Every clause earns its place with no redundancy or filler.

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 3-parameter read tool with no output schema, the description covers purpose, batching limit, failure handling, and pricing. It leaves the async flag and the returned result format unaddressed, which are minor gaps given the absence of an output schema.

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 67%, establishing a baseline of 3. The description's 'up to 20' and 'trimmed to your character limit' essentially restate what the urls and max_chars schema descriptions already say, and the async parameter remains undocumented in both places, so it adds little meaning beyond structured fields.

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 verb (read) and resource (web pages) with an explicit scope cap (up to 20) and the transformation performed (cleaned to text). However, it does not name or contrast with sibling tools like scrape, crawl, or extract, so the agent must infer the differentiation from the 'instead of 20 separate calls' phrasing rather than from an explicit sibling reference.

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?

The 'in one call (instead of 20 separate calls)' clause gives a clear efficiency-based context for choosing this tool over repeated single reads. It stops short of naming specific alternatives or stating exclusions (e.g., when to prefer scrape or crawl for single pages), so it is good context without full routing guidance.

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