cacheout_smart_clean

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

Annotations already mark destructiveHint=true. The description adds valuable context: the priority order of caches, that the server stops upon meeting the target, and the dry_run option. It does not contradict annotations and enhances understanding of side effects.

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 well-structured with a numbered priority list, example usage, and return format. It is front-loaded with the purpose. Minor redundancy could be trimmed, but overall efficient.

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?

The description explains the cleaning order, dry-run preview, and provides a sample return JSON. It covers most important aspects for an AI agent to use the tool effectively, though details about the 'cleaned' and 'skipped' fields are left to the output schema.

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 omits the 'free_memory' parameter, mentioning only target_gb, dry_run, and include_caution. The input schema has comprehensive descriptions for all four parameters, so the description adds little value and is misleading by omission.

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 frees disk space by clearing caches in priority order, with a specific verb and resource. It explicitly positions itself as the primary tool for disk pressure management, distinguishing it from siblings like cacheout_clear_cache and cacheout_scan_caches.

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 explains when to use the tool (low disk space, need room for builds/swap) and provides a typical use case. It does not explicitly state when not to use it or compare with alternatives, but the context is clear enough for an AI agent to decide.

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