Safe Server Resource Cleanup (v1.6.0)

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

Annotations already indicate non-destructive and idempotent behavior; the description adds valuable context about the safety threshold (>70% disk usage requirement) and specifically what is pruned (dangling Docker images, stale git branches), which goes beyond the annotations.

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 that conveys all key information with 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?

The description covers the main actions and conditions, including the threshold and force option. However, it does not mention return values or behavior when the threshold is not met without force, which would be helpful for a standalone tool without output schema.

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 both parameters documented. The description does not add significant meaning beyond the schema; it only references the force parameter indirectly. 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?

The description clearly states the tool checks server disk usage with a specific threshold (>70%) and performs non-destructive pruning of dangling Docker images and stale git tracking branches. This specific verb and resource combination distinguishes it from siblings like inspect_server or prepare_new_server.

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 usage when disk usage is high (>70%) or with force flag, but does not explicitly state when to use this tool versus alternatives, nor when not to use it. There is no mention of alternatives among siblings.

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