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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description earns credit for the additional context it supplies: the required stories API scope and the English-fallback behavior for untranslated fields. It does not discuss pagination edge cases, but those are documented 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?

Two short sentences with no filler, and the scope requirement is front-loaded after the identifying clause. It is efficient, though its brevity borders on under-specification rather than maximal usefulness.

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 tool with five parameters, two enums, and an output schema, the description covers auth scope and language fallback but omits the scoping of results (global vs. per-user/workspace) and any routing versus the many sibling list tools. The presence of an output schema removes the need to describe return values, keeping this at a minimum-viable 3.

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 schema already explains lang, limit, cursor, metric, and window semantics including clamping and 400 behavior. The description adds no parameter detail beyond reiterating the English fallback, so the baseline of 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 names the resource ('Newsroom momentum') and the ranking mechanism plus metric version, so an agent knows it is a ranked list. However, it is essentially a restatement of the title with no verb like 'list' or 'return' and no differentiation from siblings such as stories_list, search_list, or brief_get. Purpose is inferable but not crisply stated.

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?

The only usage signal is 'Requires the stories API scope,' which is an auth prerequisite rather than guidance on when to choose this tool over stories_list or search_list. There is no statement of when-not-to-use or which alternative handles unranked or search-based retrieval.

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