cleanup_media_cache

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

Annotations indicate readOnlyHint=false (a write/mutating operation) and the description expands on this by stating it cleans up files and frees disk space. However, it does not disclose whether the deletion is permanent, irreversible, or whether it affects only media files or also metadata. The description adds some context but not enough to fully understand the destructive nature beyond what annotations already imply.

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 repetitive, using phrases like 'cleaning up old cached media files', 'clean up storage space', and 'cache becomes too large' multiple times. It is not overly long, but every sentence does not earn its place; the final sentence adds little. It is front-loaded with 'REQUIRED' which is somewhat bold but acceptable.

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 tool's simplicity (one parameter) and lack of output schema, the description covers the basic purpose and usage. However, it lacks explanation of the max_age_days parameter, the permanence of deletion, and any side effects. It is adequate for basic understanding but leaves gaps for correct invocation, especially since schema coverage is 0%.

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 schema has one parameter, max_age_days, with 0% coverage from the description. The description does not mention this parameter at all, nor explain how age is determined or the effect of changing the default. Since schema coverage is 0%, the description should compensate, but it fails to provide any parameter guidance.

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's purpose with a specific verb ('cleaning up') and resource ('old cached media files'), and explicitly mentions images and videos. It distinguishes itself from sibling tools like get_cache_stats and search_cached_media by focusing on the deletion/cleanup action.

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 provides clear usage context: use when users want to remove old cached media, clean up storage space, or when cache becomes too large. However, it does not explicitly state when not to use the tool or name alternatives, though siblings are obviously different. This is good but not fully explicit.

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