bing_news

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

Discloses that results are fetched from public Bing news HTML/async pages and may return 503 on challenge pages. This warns agents about reliability. No annotations provided, so description carries the burden well. Could mention rate limits or data freshness, but still strong.

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 sentences with no waste. First sentence states purpose immediately. Second sentence adds critical defaults and error behavior. Front-loaded and efficient.

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?

Covers purpose, failure mode, and locale defaults. No output schema exists, so description should hint at return structure (e.g., fields included in normalized results). Missing that context. Adequate but with gaps for a no-output-schema tool.

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 clear descriptions. The description reiterates locale defaults already in schema, adding no new semantic meaning. Baseline 3 is appropriate.

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 'Search Bing news results' with a specific verb and resource. It distinguishes from sibling Bing tools (images, search, videos, suggest) by focusing on news.

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?

Provides context about locale defaults and potential 503 errors, but does not explicitly guide when to use this tool versus alternatives like google_news or general bing_search. No exclusions or when-not-to-use advice.

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