clean_workspace

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

No annotations are provided, leaving full burden on description. It discloses the destructive action (delete), but does not mention safety, permissions, reversibility, or impact on active sessions. Basic transparency is present but incomplete.

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 sentences: first states the primary action, second adds optional parameter and benefit. No wasted words.

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?

Given the simple tool (1 parameter, no output schema), the description covers key aspects: what it deletes, optional behavior, and benefit. Missing details about return value or edge cases, but adequate for the scope.

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 one numeric parameter 'keep'. The description adds the default value (0 = remove all) and clarifies the behavior ('keep N most recent'), enhancing schema information.

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 'Delete', the resource 'old scratch session directories', and the optional parameter. It distinguishes from sibling tools by focusing on cleanup of temporary compilation artifacts.

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 when to use (to free disk and keep workspace tidy) but lacks explicit guidance on when not to use or alternative approaches. Sibling tools suggest different purposes, so context is clear.

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