Stop Gradle daemons

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

No annotations are provided, so the description must carry the full behavioral burden. It states the core behavior (stopping daemons) but does not disclose potential side effects like interrupting running builds or whether daemons restart automatically. It adds the usage hint but lacks safety/caveat details.

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, focused sentence. The action is front-loaded, and the usage guidance is provided as a concise parenthetical. No unnecessary 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?

For a simple command with one optional parameter and no output schema, this description sufficiently covers what the tool does and when to use it. It does not explain return values, but that is not required given no output schema. The description is complete enough for an agent to select and invoke the tool correctly.

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 input schema already describes the lone parameter 'projectDir' with 'Project root (defaults to session)' and coverage is 100%. The description does not add further meaning about parameters, though it refers to 'the project's' which implies project scope. This meets the baseline for full schema coverage.

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 action: 'Stop the project's Gradle daemons'. This is a specific verb+resource that distinguishes it from sibling tools like build or clean. The parenthetical 'use when a build hangs or to free memory' further clarifies its purpose.

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?

It explicitly gives usage context: 'use when a build hangs or to free memory'. This tells the agent when to invoke it, though it does not mention alternatives or exclusions. Still, the guidance is clear and actionable.

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