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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds valuable context: it discloses the time window, role-based output, and the locale parameter's effect. It does not contradict annotations. Minor gap: it doesn't mention ordering or pagination, but the output schema covers the return value.

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?

The description is two sentences: the first states the core functionality, and the second adds critical role-based details. Every sentence is necessary and informative, with no redundant or filler content.

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?

Given the existence of an output schema, the description focuses on behavior rather than return values. It covers the time window, role-based differences, and locale usage. It is fairly complete for this simple tool, though it could mention that results are sorted by publish date.

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 33% (only locale has a description). The description explains that days refers to 'past X days' and locale should be the caller's language (ignored for admins). However, it does not add meaning to the limit parameter beyond what the schema provides, and the days parameter's description is minimal.

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 clearly states it returns published news from the past X days, with a default of 90. It specifies the distinction between administrator and non-administrator outputs (bilingual vs. single locale), making the purpose specific and differentiating it from sibling tools like get_news_by_id.

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 description indicates the tool is for retrieving recent news and explains the different behavior for admins versus other accounts. However, it does not explicitly state when to use this tool over alternatives like get_news_by_id or search_explainers, though the context implies listing instead of searching or getting by ID.

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