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

With no annotations, the description carries the full burden, and it does disclose real behavioral context: results come from free DuckDuckGo by default or a paid Brave/Serper backend when configured, which signals varying result quality and quota behavior. It omits result-count limits, failure modes, and whether query syntax/operators are supported.

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?

Two compact sentences with the core purpose front-loaded and the return/backend details following. Every clause adds information; nothing is repetitive or padded.

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 one-parameter lookup tool with no output schema, the description covers purpose, result structure, and backend variability, which is close to sufficient. It would be complete with a note on how many results to expect and how this relates to the fetch/extract pipeline.

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 0% for the single `query` parameter, so the description must compensate and does not. It never explains whether queries accept operators, quoted phrases, site filters, or backends-specific syntax, so the agent learns nothing about the parameter beyond its name.

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?

"Live web search" names a specific verb and resource, and the definition goes further by describing the return shape ({title, url, snippet}) and which backend serves results. It stops short of distinguishing the tool from siblings like fetch or extract, which is the missing piece for a 5.

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 explicit when-to-use or when-not-to-use guidance. An agent cannot tell from this text why it should choose search over fetch or extract, nor what to do with the returned URLs (presumably hand them to fetch), leaving routing to inference.

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