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

Goes well beyond annotations by explaining the internal process (HackerNews + Wikipedia + DuckDuckGo simultaneously, then Groq distills) and disclosing cost ($0.05) and auth requirement (API key). Annotations already state readOnly and openWorld, and the description adds complementary detail without contradiction.

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?

Three sentences, front-loaded with purpose, then usage guidance, process, and cost/auth. Every sentence earns its place with no wasted words.

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?

Fully describes the tool's behavior, output type (authoritative answer with cited sources), costs, authentication, and when to choose it over alternatives. No output schema exists, but the description enough sets expectations for return content.

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 schema fully describes the 'query' parameter with its own example and guidance, so the description adds no additional param-specific semantics. Baseline 3 is appropriate since schema coverage is 100%.

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 clearly states the tool performs a 3-parallel-source search with Groq synthesis to produce one authoritative answer with cited sources. It explicitly contrasts with web_search, making its unique purpose and resource immediately clear.

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?

Explicitly says 'Use instead of web_search when you need a definitive answer, not just links,' providing direct alternatives and usage context. Also mentions cost and API key requirement, which set expectations for when to invoke.

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