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

No annotations are provided, so the description carries the full disclosure burden. It reveals the aggregation of two sources, which is genuinely useful behavioral context, but says nothing about whether results are merged or ranked, rate limits, network calls, or that the limit is capped at 30 (that detail lives only in the schema).

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?

A single 14-word sentence leading with the verb and resource, with the differentiating detail (the two sources) front-loaded. Nothing is padded and nothing needs to be trimmed.

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 two-parameter, all-optional read tool with no output schema, the description is minimally adequate but leaves the main ambiguity unresolved: how get_trending differs from get_top_news, and whether the limit applies per source or to the combined result. There is no output schema to offload those questions to.

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 both parameters (limit, topic, including their defaults and allowed topic values) are already fully documented in the schema. The description's 'for a given topic' merely restates the topic parameter without adding format or semantics, so the baseline 3 applies.

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 (get) and resource (trending news) and even names the two upstream sources, Hacker News and The Guardian. It does not, however, distinguish itself from the sibling get_top_news, so an agent cannot tell from the description alone which of the two it should call.

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 guidance on when to use this rather than get_top_news or search_guardian, no exclusions, and no prerequisites. The mention of 'a given topic' implies the topic parameter is the selector, but that is schema-level information, not usage guidance.

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