arcane_prune_images

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

With no annotations, the description carries full responsibility for disclosing safety and side effects. It does not mention that pruning is destructive, irreversible, or what 'unused' means, leaving significant behavioral ambiguity for a pruning operation.

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 redundant wording. Every word contributes to the core purpose.

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?

While the tool appears simple with one parameter, it is destructive (pruning) and lacks any disclosure about consequences, scope of removal, or return values. The absence of annotations and output schema makes the description insufficient for an agent to fully understand the tool's impact.

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 schema covers the single parameter (environmentId) with a basic description. The tool description adds context by linking pruning to 'the environment', but it does not elaborate on parameter expectations, such as environment existence or format, beyond the schema.

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 verb 'prune' and the resource 'unused images' within the scope of 'the environment', which is specific and distinguishes it from sibling tools like remove_image, prune_volumes, and prune_system.

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 guidance is provided on when to use this tool versus alternatives such as arcane_remove_image for specific images or arcane_prune_system for broader cleanup. The description implies usage but does not state conditions or exclusions.

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