get_cleanable_estimate

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

Without annotations, the description carries the burden. It correctly conveys that the tool is a read-only estimate (non-destructive) and returns a breakdown. It does not mention limitations or permissions, but for a 0-parameter read tool, this is adequate.

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?

Two concise, front-loaded sentences with zero wasted words. The first sentence states the primary action and scope, the second elaborates on the return format.

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 is complete for a 0-parameter tool. It explains the input (none), the action (estimate), and the output (breakdown by category). Considering no output schema, this is sufficient for an agent to understand and invoke the tool correctly.

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?

No parameters exist, and schema coverage is 100%. The description adds value by explaining that the return value is a breakdown by specific categories (caches, logs, Xcode data, trash, etc.), which compensates for the lack of output schema.

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: estimating cleanable space via One Touch Clean and returning a category breakdown. This distinguishes it from sibling tools like get_large_files (lists large files) and get_storage_breakdown (general storage breakdown).

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 implies usage before performing One Touch Clean, but does not explicitly state when to use this tool versus alternatives like get_storage_breakdown or one_touch_scan. No guidance on conditions or exclusions is provided.

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