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

Read-only and non-destructive behavior is already covered by annotations, so the description adds limited new behavioral detail. It does indicate that the output includes organic results and related searches, which is useful but minimal.

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?

Two short sentences front-load the core action immediatelyadian and mention the key differentiator. No filler or repetition of schema fields.

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 simple, read-only search tool with 100% schema coverage and strong annotations, the description sufficiently conveys purpose, output type, and sibling differentiation. It could be slightly more explicit about return shape, but the absence of an output schema and the simple nature of the tool make the current description adequate.

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 100%, so all four parameters are already documented. The description adds no additional parameter-specific meaning beyond confirming the general purpose of 'q'.

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 names a specific action and resource ('Search the web using Bing') and explicitly contrasts itself with Google, distinguishing it from sibling search tools like google_scholar or google_images_light.

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?

Clear context is provided: this is a web search tool using Bing and is an alternative to Google. It does not explicitly enumerate exclusions or state precisely when to prefer it over other sibling tools, but the 'different ranking algorithms and results' note gives useful selection criteria.

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