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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description still adds real behavior: results are scored with per-article value tiers and sentiment, ordered newest first, and cost 0.5 points per call — a billing disclosure not present in any structured field.

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?

Three tight sentences with the core identity front-loaded, then filtering, then pagination, then cost. No filler and nothing buried at the end.

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?

With no output schema and seven optional filter parameters, the description correctly sketches the return shape (article with symbols, value, sentiment) and the pagination model, which is what an agent needs to iterate pages. Minor gaps remain around result volume/rate limits beyond the per-call point cost, but the essentials are present.

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 86%, so the schema already documents asset, limit, since, cursor, symbols, min_value and sentiment. The description's 'since for new, cursor for older pages' largely restates what the schema says ('next_cursor from the previous answer', 'only items newer than this'), so it adds little beyond baseline.

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 verb+resource ('scored news stream behind Market Pulse') and describes what each article carries (symbols, value, sentiment), which is far more than a restated name. It implicitly separates itself from get_news_article (single article) and news_translate by framing the result as a stream, though it never names a sibling explicitly.

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?

Gives operational guidance for two parameters ('use since to fetch only what is new, cursor for older pages') but says nothing about when to choose this tool over get_news_article, get_pulse_events, or news_translate. Usage is implied by the news-stream framing rather than stated.

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