delete_all_app_caches

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

No annotations provided, so the description carries full responsibility. It states that it deletes 'all stored caches', which is destructive, but does not mention irreversibility, required permissions, or side effects. The return value is described, but behavioral implications are missing.

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 very concise (two lines for args and returns), but at the cost of missing important usage and behavioral context. It is not wordy, but could better balance brevity with completeness. The structure is clear but minimal.

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 (implied by description mentioning return value), the description explains the return format (list of cache IDs and a message). However, for a destructive tool with a sibling, the description lacks context about when to use it, potential impact, and alternatives. It is adequate but not comprehensive.

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 single parameter 'app_id' is described as 'The application identifier' in the description, which adds basic meaning beyond the schema's title 'App Id'. However, the description does not elaborate on format, validation, or examples. Given 0% schema description coverage, the description provides minimal but acceptable clarification.

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?

Clearly states the action ('Delete all caches') and resource ('for an application'). However, it does not differentiate from the sibling tool 'delete_app_cache', which likely deletes a single cache. The description could clarify that this deletes all caches vs. a specific one.

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 guidance on when to use this tool versus alternatives. Since it deletes all caches, it should warn about destructive consequences or mention when it is appropriate. The sibling 'delete_app_cache' suggests a more targeted alternative, but the description doesn't address this.

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