clean

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

No annotations provided, so description must disclose behavioral traits. It does not indicate whether the operation is destructive, safe, or has side effects. The phrase 'clean cache files' gives no insight into what actually happens (e.g., deletion, invalidation).

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?

Extremely concise (3 words) but at the expense of clarity. For a tool with two parameters, one a nested object, this is under-specification. Not all concise descriptions are effective.

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?

No output schema, and the description fails to explain what cleaning cache entails, expected outcomes, or warnings. With moderate complexity (2 params, nested object), this is incomplete.

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 coverage is 100% (both parameters have descriptions). The tool description adds no new meaning beyond the schema. Baseline 3 is appropriate.

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?

Description 'Clean cache files' states verb and resource but is vague. It does not specify what kind of cache (e.g., build cache, dependency cache) or how it differs from sibling tools like 'format' or 'lint' that might also involve maintenance tasks.

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?

No guidance on when to use this tool vs siblings. No mention of prerequisites, when-not-to-use, or alternatives. Sibling tools include 'check', 'format', 'lint', etc., but no context is provided to help an agent decide.

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