bing_top_queries

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

No annotations provided, so description must cover behavioral traits. Only mentions 'US traffic' but lacks details on data freshness, pagination, rate limits, or what defines 'top'. Minimal transparency beyond basic function.

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?

Extremely concise: two-line summary plus two parameter lines. Front-loaded with essential info; every sentence adds value without redundancy.

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?

Explains returned metrics (clicks, impressions, CTR, position) and parameter usage. Output schema exists, so return format details aren't needed. However, lacks context on timezone, data source, or definition of 'top' queries.

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%, but description adds format (YYYY-MM-DD) and actual defaults (28 days ago, today) that are missing from schema. Provides clear, actionable parameter guidance beyond schema fields.

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?

Clearly states it retrieves 'top Bing search queries' with specific metrics (clicks, impressions, CTR, position) and scope (US traffic). Distinguishes from siblings like 'bing_keywords' by specifying 'top' and geographic scope.

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?

No explicit guidance on when to use this tool vs alternatives. Does not mention prerequisites, limitations, or appropriate contexts. The description only states what it does, not when to use it.

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