bing_search

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

The description adds context beyond annotations by revealing that searches occur through the user's real Chrome session, implying the use of the user's logged-in state and potential personalization. This complements the readOnlyHint and idempotentHint annotations. No contradictions with annotations.

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 a single, front-loaded sentence that efficiently conveys the tool's core purpose. Every word contributes meaning without redundant details.

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?

The tool is relatively simple, and the output schema exists, so return format need not be described. However, given the presence of many sibling search tools, the lack of usage guidelines limits completeness. The description covers the core functionality but leaves the selection context unaddressed.

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?

The schema has 0% description coverage, and the tool description does not explain the 'keyword' or 'limit' parameters. While the parameter names are self-explanatory, the description fails to clarify how 'limit' behaves (e.g., max results) or any constraints on 'keyword'. The description does not compensate for the missing schema descriptions.

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 the tool searches the public web using Bing, with the distinctive detail of using the user's real Chrome session. This differentiates it from sibling search tools like google_search or sogou_search by specifying the engine and session context.

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 is provided about when to use this tool versus alternatives. While the description implies using it for Bing searches, it does not mention sibling tools or provide criteria for choosing Bing over other search engines.

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