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

With no annotations, the description carries the full behavioral burden. It discloses boundedness, paging, total count, result fields, and per-call cost, which is meaningful. However, it does not discuss rate limits, authentication needs, query semantics, or failure behavior, so some behavioral context remains undisclosed.

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 a single tightly-worded sentence with no filler. Every clause adds value: the resource scope, the return shape, paging behavior, and cost are all compressed without redundancy.

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 simple read-only search tool, the core call is mostly understandable: the query is obvious, and limit/offset are inferable from the schema. But the absence of sibling-routing guidance and parameter-level detail, combined with no annotations or output schema, leaves meaningful gaps in the overall contextual picture.

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 0%, so the description must compensate for missing parameter explanations. It mentions paging and a total count, which hints at offset behavior, but it does not explain query semantics, what limit controls, or how offset interacts with paging. The schema's min/max/defaults are useful but not accompanied by human-readable parameter guidance.

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 names a specific action ('Run a bounded web search'), a resource ('public encyclopedic reference index'), and the output fields ('title, URL and snippet per hit'). It is clearly distinguishable from siblings like web_extract and tweets_search, but it does not explicitly call out what it is not or name an alternative.

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?

There is no guidance on when to prefer this tool over web_extract, research_answer, tweets_search, or other search-like siblings. The intended use is only implied by the resource type, with no exclusions or alternative routing advice.

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