bing_serp: GET /

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

No annotations are provided, so the description carries full burden. It discloses the output elements (organic results, related searches, answer boxes, pagination metadata) and input parameters. However, it omits potential side effects, rate limits, or authorization requirements. The description implies read-only behavior but does not confirm.

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 two sentences: first lists capabilities, second lists return types and use cases. It is front-loaded with the core action and contains no fluff. Every phrase is informative.

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?

Given no output schema and no annotations, the description covers input parameters comprehensively and explains the expected output (organic results, related searches, etc.). It could discuss error handling or edge cases but is generally complete for a search tool with many parameters.

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 100%, meaning all parameters have descriptions. The description adds grouping context (e.g., 'geo targeting (location/lat/lon)') but does not significantly enhance meaning beyond the schema. Baseline 3 is appropriate as the description adds modest value.

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 explicitly states 'Get Bing Search Results' and details the function: 'Fetches Bing SERPs for a query'. It lists specific capabilities (geo targeting, market, safesearch, filters, etc.) and clearly differentiates from siblings by being Bing-specific, whereas siblings are for Google, Amazon, etc.

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 provides explicit use cases: 'Use for SEO rank tracking, SERP feature monitoring, Bing-specific visibility audits, and training/eval data for search agents.' It also enumerates parameters for geo targeting and filters, giving context. However, it does not explicitly contrast with sibling tools or state when not to use.

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