Git clean preview

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds important safety context by requiring confirm=true for execution. It does not explain specifically that git clean removes untracked files/directories, but the confirmation gate meaningfully supplements the destructive annotation.

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 with no filler: it states the mode, the default behavior, and the safety requirement efficiently. Every part earns its place.

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?

For a destructive command with no schema-level parameter descriptions, the description is incomplete. It omits what git clean actually removes and leaves path/dirs semantics undefined, even though the confirmation gate is well handled.

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 description coverage is 0%, so the description must compensate, but it only clarifies confirm and dry_run. The path and dirs parameters remain semantically unexplained, leaving an agent to guess their meaning and role in the operation.

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 identifies the operation as previewing or executing git clean, with an explicit confirmation requirement. It is specific enough to distinguish from other git operations like checkout or reset, though it does not explicitly name a sibling alternative.

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 gives clear operational context: preview via dry_run is the default, and actual execution is gated on confirm=true. It does not spell out when to choose git_clean over other git tools, but the safety gating and mode distinction provide useful guidance.

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