SerpApi search (dashboard)

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

Annotations already cover read-only, non-destructive, and open-world hints. The description adds behavior beyond these: it describes the interactive rendering in conversation and the automatic selection of engine-specific dashboards (e.g., google_flights), which is valuable context. No contradiction with annotations.

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 with zero fluff. The key differentiator (dashboard variant) is front-loaded, followed by output details and usage guidance. Every sentence earns its place.

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 variant tool, the description is complete: it states what it returns, when to use it, and where to get parameter details. It does not mention pagination or error handling, but these are not critical for a read-only dashboard tool with annotations already covering safety.

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 has one opaque `params` object with 0% coverage. The description compensates by stating 'Same params as `search`', directing the agent to the sibling's schema for parameter details. This is a pragmatic and effective way to convey parameter meaning.

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 it is an interactive dashboard variant of `search`, enumerating the specific outputs (summary metrics, source breakdown chart, results table with expandable detail panel). This distinguishes it from the sibling tools `search` and `search_table` without ambiguity.

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 says 'Use for a richer visual overview of a query's results', giving clear context for when to select this tool. It also notes 'Same params as `search`', implying the simpler `search` tool may be used for non-visual needs, though it does not explicitly name alternatives or exclusions.

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