bing_serp: GET /

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

Without annotations, the description carries full responsibility. It explains that the tool fetches SERPs, accepts various parameters (geo, market, safesearch, filters, device type, pagination), and returns organic results, related searches, and answer boxes. This provides sufficient behavioral insight without side effects or rate limits.

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 concise yet comprehensive, front-loading the core function and then listing capabilities in a structured list-like format. No redundant or vague statements; every sentence adds value.

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 11 parameters and no output schema, the description covers all essential aspects: input parameters, return types, and use cases. It even provides example filter syntax. This makes the tool easy to understand and use without additional documentation.

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% with descriptions, but the description adds value by grouping parameters (e.g., 'geo targeting (location/lat/lon)') and explaining their purpose in context. It highlights key constraints like 'count up to 50' and 'first offset' for pagination, which aids understanding beyond the schema.

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 'Get Bing Search Results' and details the functionality: fetching SERPs with geo targeting, market, etc. It lists return types (organic results, related searches, answer boxes) and specifies use cases like SEO rank tracking. This distinguishes it from sibling tools focused on other platforms (e.g., Google, Amazon).

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 explicitly lists intended use cases: 'SEO rank tracking, SERP feature monitoring, Bing-specific visibility audits, and training/eval data for search agents.' It provides clear context but does not explicitly state when not to use or mention alternatives.

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