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

Beyond the annotations (readOnly/openWorld/non-destructive), it discloses engine rotation and fallback semantics, that a pinned engine failure surfaces as your error instead of being routed around, that an empty result list is a valid answered search, and that such a search is not charged. It also names the auth mechanism (Geonode API key via X-Api-Key header), which no structured field provides.

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?

A single dense paragraph that front-loads the core action, then capabilities, then defaults, then return shape and auth, with no filler sentences. Every clause carries information an agent would otherwise have to infer, even where it overlaps the schema.

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?

With no output schema, the description compensates by enumerating the return payload (result list, serving engine, query suggestions, spelling correction). Combined with the auth requirement, billing note, and fallback behavior, an agent has everything needed to call this correctly and interpret common edge cases like empty 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?

The description restates the meaning of locale format, page, safe-search, time_range, and engine, and crucially explains the top-level `api_key` parameter, which carries no description in the schema despite the reported 0% top-level coverage. Most individual parameter detail is duplicated by the nested SearchRequest property descriptions, so it reinforces rather than extends the schema on those 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?

The description opens with a specific verb and resource ("Run a web search and return ranked results"), so there is no ambiguity about what the tool does. It implicitly separates itself from sibling `crawl`, `extract`, and `map` by being a plain query-to-results lookup, but it never explicitly contrasts with `search_job`/`search_jobs`, which is the nearest alternative an agent must choose between.

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 gives real decision guidance for one parameter cluster: default engine rotation is stated as what "most callers want," and pinning is framed as trading reliability for control, which is a usable when/when-not rule. However, there is no guidance on when to choose this synchronous search rather than the sibling `search_job` or `batch` tools, so tool-level routing is left to inference.

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