purge_instances

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

No annotations are provided, so the description carries full burden. It mentions 'free up disk space' implying a destructive action, but it does not disclose that purged instances are permanently removed and cannot be recovered, nor any other behavioral traits like permission requirements or rate limits.

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 sentence with no unnecessary words. It is front-loaded and efficient, earning its place without redundancy.

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 no parameters and a simple purpose, the description is largely complete. It specifies the scope ('all deleted Multipass instances') and the benefit ('free up disk space'). An output schema exists, so explaining return values is not required. Slight gap: no mention of irreversibility, but overall comprehensive enough.

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 tool has zero parameters, so no parameter semantics are needed. The description does not need to add meaning beyond the schema, which is already complete (100% coverage). A baseline of 4 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 'Purge all deleted Multipass instances to free up disk space,' specifying the verb 'purge' and the resource 'deleted Multipass instances.' It distinguishes from sibling tools like 'delete_instance' and 'recover_instance' by targeting only deleted instances.

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 wanting to free disk space by removing deleted instances, but it does not explicitly state when to use it versus alternatives like 'recover_instance' (to restore) or 'delete_instance' (for active instances). No when-not or alternative guidance is provided.

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