discover_clean

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

The description indicates a destructive action ('Remove') but does not disclose what the 'discover stash directory' contains, whether the operation is reversible, or if specific permissions are needed. With no annotations provided, the description carries the full burden of behavioral disclosure, which is insufficient.

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 minimal, consisting of one sentence. While concise, it omits essential details that would make it more helpful. It is not overly verbose, but the brevity compromises completeness.

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 tool has only one parameter and an output schema is present, the description need not explain return values. However, it fails to provide context about the nature of the 'stash directory', its lifecycle, and when cleanup is appropriate. The description feels incomplete for a destructive operation.

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 sole parameter 'cluster_slug' has no description in the schema (0% coverage), and the tool description adds no meaningful context about it. The description fails to explain the format, allowed values, or how to obtain the correct slug, leaving the agent without necessary guidance.

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 removes the discover stash directory for a cluster. It uses a specific verb ('Remove') and resource ('discover stash directory'), and the scope ('for a cluster') is explicit. This distinguishes it from other discover-related siblings like discover_new or discover_continue.

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 is provided on when to use this tool versus alternatives. The description lacks context on prerequisites, such as whether a discover process must be complete or if stash cleanup is safe to perform at any time. There is no mention of when not to use it.

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