compare_search_engines

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. It discloses important constraints: deltas only appear when both providers expose the same exact observed window, and positions remain side-by-side due to different provider semantics. It does not address permissions, rate limits, or read-only nature, but the key comparability caveats are surfaced.

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?

The description is tightly written: one sentence for purpose, one for delta behavior, one for position semantics. It is front-loaded with the core action and contains no filler.

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 exists, so return values need not be explained. The description adds meaningful comparison caveats, but it leaves all input parameter semantics undocumented and provides no usage context. For a 5-parameter tool with 0% schema description coverage and no annotations, this is only minimally complete.

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% across 5 parameters. The description vaguely hints at the dimension values by saying 'query or page metrics,' but it does not name or explain google_site, bing_site, days, limit, or dimension. With no parameter descriptions in the schema, the description fails to compensate.

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 states a specific verb and resource: comparing Google and Bing query or page metrics. It is clear enough to distinguish from most sibling tools like compare_search_periods, but it does not explicitly name any alternative or sibling to differentiate from.

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?

The description gives a caution about causality and comparability but does not say when to use this tool versus alternatives such as bing_query_stats, bing_page_stats, or get_search_analytics. No prerequisites, exclusions, or routing guidance are provided.

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