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

With readOnly/openWorld/idempotent already declared, the description still adds substantial behavior: primary Bing News RSS with automatic retry on empty pages, Brave News fallback, source named in the response, 404-not-charged on empty results, and x402 USDC payment terms with a PaymentRequired object when unpaid. That is exactly the runtime context annotations cannot carry.

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?

Dense but front-loaded: usage triggers first, then return shape, then parameter hints, then source/error/payment details. Nearly every sentence carries load, though the long single-paragraph run-on structure slightly hurts scannability.

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 6-parameter, no-output-schema tool, the description covers return fields (title, direct URL, publisher, ISO timestamp, snippet, image), result limits, source and fallback behavior, empty-result handling, and billing. An agent has everything needed to call and interpret it correctly.

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 the baseline is 3; the description largely restates sort/freshness/market values already documented in the schema. It adds minor framing (market selects regional editions, freshness limits article age) but omits page/count and offers no new syntax 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 states a specific verb and resource — news search returning articles — and enumerates concrete use cases (current events, press monitoring, recent coverage, digests). The title frames it against web search and autocomplete, but the description itself never names the sibling tools, so differentiation relies on the title.

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?

It gives four clear triggers for when to use this tool (current events, monitoring, pre-answer coverage checks, digest building), which is strong positive guidance. It stops short of naming when NOT to use it or routing to the web/suggest siblings for non-article queries.

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