cleanup_media_cache

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

Annotations indicate readOnlyHint=false, so the description correctly implies a mutation operation. It adds that the tool 'removes old cached media' and 'frees disk space,' but it does not disclose whether deletion is permanent/reversible, whether it requires special permissions, or what happens to associated metadata. For a deletion tool, this lacks critical safety info, but the core action is conveyed.

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 redundant and has fluff: the opening 'REQUIRED' is unexplained, 'cleaning up old cached media files' is repeated as 'cache maintenance,' and 'Essential for' adds little. It could be trimmed to one or two sentences without losing meaning. It is not overly long, but not tight either.

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 optional parameter and no output schema, the description covers the primary use case and when to trigger it. However, it omits the parameter's role, any return value or success/failure indications, and the irreversible nature of deletion. Given the low complexity, this is borderline adequate but leaves room for improvement.

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 input schema has one parameter, max_age_days, and schema_description_coverage is 0%. The description makes no mention of this parameter, leaving the agent to infer its purpose from the name alone. Since the description does not compensate for the low coverage, the parameter's meaning (how age is defined, default behavior, impact of changing it) remains ambiguous.

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 identifies the tool as cleaning up old cached media files (images and videos) and freeing disk space, which is a specific action on a specific resource. It distinguishes itself from sibling tools like analyze_ad_video and search_cached_media by focusing on deletion/cleanup rather than analysis or search.

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 explicitly states when to use the tool: 'when users want to remove old cached media, clean up storage space, or when cache becomes too large.' It provides clear context and a user-intent trigger, though it does not explicitly mention when not to use it or suggest alternative sibling tools such as get_cache_stats for checking cache size.

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