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

With no annotations, the description carries the full burden and does so well: it discloses output shape, the 4,000-character truncation per page, partial-failure semantics ("a page that fails is marked, the rest still ship"), provider-failure billing, and the $0.02 USDC x402 payment requirement. These are exactly the traits an agent cannot get from structured fields.

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?

Front-loaded with the selection condition, then Input/Output/failure/pricing in a tight telegraphic style. The sample query string is marginally useful but the description stays dense with no filler sentences.

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, so the description must explain returns — and it does, specifying title/URL/date per result plus Markdown body for the top 3 with truncation and failure marking. Combined with cost and payment details, an agent has everything needed to call 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 coverage is 100% so the baseline is 3, but the description adds value beyond the schema: it supplies the 1-10 range and default 5 for max, and enumerates time_range values (day, week, month, year) that the schema leaves as a free-form string with no enum. That is a real gain for correct invocation.

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 verb+resource is concrete: search and read in one call, returning top results plus Markdown page text for the top 3. This implicitly separates it from sibling web_search (search only) and convert_to_markdown (read only), but it never names those siblings explicitly, so the differentiation is inferred rather than stated.

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?

"Use when an agent needs to search and read in one call" gives a clear selection condition tied to the combined capability. It stops short of an explicit when-not clause or naming web_search as the cheaper alternative when page text is unnecessary.

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