news_media_briefing

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, so no contradiction. Description adds cache TTL behavior (60 min per topic) and mentions 'use_cache' parameter, which goes beyond annotations. However, no disclosure of rate limits or quota effects.

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?

Description is two sentences: first sentence states purpose and cache behavior, second lists arguments and return type. It is concise and front-loaded. However, it mixes German and English unnecessarily.

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 complexity of 5 parameters and output schema existence, description is partially complete. It explains caching and brief structure, but omits details like source_country format or days_back range meaning. Output schema covers return value, so minimal need for return description.

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 has 0% description coverage, so description must compensate. It only lists parameter names (topics, language, etc.) without explaining their semantics beyond defaults. For example, 'source_country' default 'ch,de,at' is not explained. Schema itself lacks descriptions for properties.

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?

Description clearly states it provides a multi-topic media briefing for a specific group (GL/KI-Fachgruppe) with cache TTL. It distinguishes from siblings like news_search or news_alert_create by focusing on aggregated briefing. Verb 'Briefing' is specific and resource is implied.

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?

No explicit guidance on when to use this tool vs alternatives like news_search or news_alert_list. It does not state prerequisites or when not to use it. The target audience hint is present but insufficient for decision-making.

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