cleanup_media_cache

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

Annotations already indicate readOnlyHint=false, so it is known to be a mutation. The description adds that it targets old cached media and frees disk space, but does not disclose irreversibility, whether files are permanently deleted, or any side effects beyond freeing space. This is minimal but not contradictory.

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 brief and front-loaded with the action. However, the closing phrase 'Essential for cache maintenance and storage management' is somewhat redundant and does not add meaningful value beyond the first sentence.

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 one parameter, the description covers purpose and usage, but lacks information about return values or specific outcomes like the number of files deleted or space reclaimed. Since there is no output schema, the description should explain what the tool returns or what happens after cleanup.

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%, and the description does not mention the max_age_days parameter or explain how it affects cleanup. The parameter name and default are in the schema, but the description does not compensate for the lack of schema-level descriptions.

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 cleans up old cached media files and frees disk space, using a specific verb and resource. It naturally distinguishes itself from sibling read-only tools like get_cache_stats and search_cached_media.

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 gives explicit context for when to use the tool: when users want to remove old cached media, clean storage space, or when cache becomes too large. It does not mention alternatives or when not to use it, but the primary use cases are clearly defined.

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