as_gradle_clean

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

Annotations already declare destructiveHint=true and idempotentHint=true. Description adds the scope of deletion ('Only touches the build/ dir.'), which goes beyond annotations. No mention of side effects, but the destructive nature is clear.

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: two sentences for purpose plus minimal Args/Returns. Front-loaded with key action, no fluff.

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 simple tool with output schema, description covers purpose, scope, and return type. Could mention prerequisites like gradlew existence but overall sufficient.

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 0% per context signals, but the input schema itself provides descriptions for both parameters. The description merely lists parameter names (project_dir, timeout) without adding new semantics. 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 clearly states 'Delete build outputs via 'gradle clean'. Only touches the build/ dir.' with a specific verb and resource, clearly distinguishing it from sibling gradle tools like as_gradle_assemble or as_gradle_bundle.

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 explicit when-to-use or alternative suggestions. The scoping comment 'Only touches the build/ dir.' implies safety but doesn't guide the agent on when to choose this over other gradle operations or related tools like as_gradle_stop.

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