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

No annotations are provided, so the description carries the full behavioral burden, yet it only vaguely states 'normalized results'. It says nothing about rate limits, caching, query length constraints, or how include_content changes behavior. Only the output schema offsets the return-format gap.

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 front-loaded sentence with no padding or repetition. However, the terseness borders on under-specification for a tool with this much nested structure rather than true economy of information.

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?

An output schema removes the need to describe returns, but for a search tool with nine undocumented nested parameters, no annotations, and many competing siblings, the definition is far too thin about when and how to call it.

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 should compensate, but it explains none of the nine nested payload fields (topic, time_range, include_domains, exclude_domains, include_content, etc.). Parameter names are largely self-descriptive, but semantics like default value meaning and mutual include/exclude behavior are undocumented.

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 (Search) and resource (the public web) plus an output trait (normalized results). It is distinguishable from social-* search siblings and page-extract, but it never names or contrasts with the closest alternatives like search-results or ai-search-data.

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 when-to-use guidance, no prerequisites, and no mention of alternatives despite a large sibling set of competing search tools. The agent is left to infer everything about routing.

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