clean_traces

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'clean' implying deletion, but does not explicitly state that the tool is destructive, irreversible, or what the default behavior (dry_run=true) entails. The 'dry_run' parameter is a hint, but the description itself lacks clarity on consequences.

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 a single front-loaded sentence that efficiently conveys the core purpose and key filters. No unnecessary words, and it is easy to parse.

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 covers the purpose and filter criteria, but lacks information about return values, default behavior (dry_run defaults to true), and any post-clean actions. Given no output schema, this leaves gaps in understanding the tool's full behavior.

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% with clear descriptions for all parameters. The description adds no additional semantic value beyond listing the filters (category, age, project). It meets the baseline for high coverage but does not enhance understanding.

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 verb 'clean' and the resource 'Claude Code traces', and specifies the selective criteria (category, age, or project). This effectively distinguishes it from sibling tools like 'wipe_traces' which likely perform bulk deletion.

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 for selective cleaning based on filters, but does not explicitly state when to use this tool versus alternatives (e.g., 'wipe_traces' for full cleanup) or any prerequisites or exclusions. Some guidance is implied but not formalized.

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