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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description contributes real behavioral context beyond that: results are relative to a per-entity baseline, so 'trending' means deviation rather than raw volume, and results are ranked. It stops short of explaining how novelty is computed, how ties or sparse-baseline entities are handled, or what the result items contain.

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?

One front-loaded sentence with no filler; every clause ('most unusual news volume', 'in the window', 'ranked by novelty against baseline') carries meaning. It is efficient, though the single clause is arguably too terse for a tool with three under-documented parameters.

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 readOnly annotations and no output schema, the safety and return-shape burden is lighter, and the description does explain what the ranking means. But for a tool whose most consequential parameter ('window') is undocumented in both schema and description, and whose ordering/tie-breaking rules are unexplained, an agent lacks enough to call it confidently outside the defaults.

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 only 33%. Only 'kind' is documented in the schema (ticker, crypto, org, central_bank, government, topic); 'limit' and 'window' have no descriptions, and the description never compensates — it does not state the accepted window syntax (only the default '24h' appears in the schema), valid units, or whether limit applies before or after novelty ranking. With low coverage, the description was the place to close this gap and does not.

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 concrete resource and ordering logic: 'Entities with the most unusual news volume... ranked by novelty against their baseline.' That is far more specific than a restated name, and an agent can tell this returns ranked trending entities rather than raw articles. It does not, however, differentiate itself from siblings like news_trending_people or news_trending_topics, leaving the scope of 'Entities' ambiguous.

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?

There is no explicit statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The closest thing to guidance is the implied use case of finding anomalous news volume, which the agent must infer from the return description alone. The sibling trending tools are never referenced, so routing between them is left entirely to guesswork.

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