bing_serp

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the paid nature (0.03 USDC on Base via x402), which is genuine behavioral context, but omits idempotency/retry semantics, auth needs, and return format.

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?

A single front-loaded sentence leading with purpose, then cost. Efficient, though the parenthetical payment detail is dense and could be split for clarity.

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 payment-gated tool with no annotations, no output schema, and half-documented params, the description covers purpose and cost but leaves the return format and the confirmNewPurchase/dedup behavior unexplained. Adequate but with clear gaps.

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 only 50%: keyword and confirmNewPurchase are documented in the schema, while language_code and location_code are bare defaults. The description adds no parameter-level meaning to compensate for the undocumented half.

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?

States a specific resource (organic Bing results) scoped to a keyword, and explicitly distinguishes itself from Google. It does not name the numerously similar siblings (serp_report, news_search, image_search), so it falls short of full differentiation.

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 phrase 'often different from Google' hints at why one might pick this engine but gives no explicit when-to-use/when-not guidance or named alternatives among the many search siblings. An agent is left to infer when Bing SERP beats serp_report or news_search.

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