news_top_headlines

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

Annotations already indicate readOnly, idempotent, non-destructive behavior. The description adds key details: caching with 15-min TTL, and that results are clustered and ranked by source count ('geclusterte Top-News nach Quellen-Anzahl gereiht'), providing significant behavioral context.

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 concise, front-loading the purpose and including an Args list. It avoids unnecessary words, though the bilingual nature (German) might slightly reduce clarity for non-German readers.

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 that an output schema exists (though not shown), the description adequately explains return format (clustered top news ranked by source count) and caching behavior. It covers key aspects: country scope, caching, and ranking, making it sufficiently complete for the tool's complexity.

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 0%; the description only lists parameter names without explaining their meaning, constraints, or defaults. For example, 'source_country' is not defined beyond its name. The description adds minimal value over the schema for parameter understanding.

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 the tool retrieves top headlines of a country ('Top-Schlagzeilen eines Landes'), with a specific verb and resource. It is distinct from sibling tools like news_search (search articles) and news_front_pages (front pages).

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 implies usage for getting top news with caching (TTL 15 min), but does not explicitly state when to use this tool versus alternatives like news_search or news_trend_radar. Usage context is implied but not clearly delineated.

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