news_cache_clear

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

The description adds value beyond annotations by explaining the confirm parameter (first call with false returns a prompt) and the return type (number of cleared entries). Annotations already indicate destructive and idempotent hints, so transparency is good.

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 extremely concise: one purpose sentence followed by clear Args and Returns sections. Every sentence adds necessary information without waste.

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 simple tool with a clear purpose and a single input object, the description covers essential aspects. It mentions the confirm parameter's behavior (though not the full details) and the return type. It does not discuss prerequisites or side effects, but the destructive hint covers that.

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?

The description's parameter section is minimal, only mentioning tool_type with 'leer = alles leeren'. It does not mention the confirm parameter, which is crucial for safe usage. Although the input schema provides full descriptions, the tool description fails to compensate adequately, especially with 0% schema description coverage.

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 clears the cache, either completely or for a specific tool type. The verb 'leert' and resource 'Cache' are specific, and the distinction between full and partial clearing distinguishes it from sibling tools like news_cache_stats.

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 clearing cache and provides the confirm parameter behavior, but does not explicitly state when to use this tool versus alternatives like news_cache_stats for monitoring. No when-not-to-use or alternative suggestions are given.

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