prune_volumes

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

Warns that the action is destructive and mentions dry_run and confirmation, but does not explain how 'unused' is determined, what volumes are affected, or the exact consequences. Without annotations, more detail is needed.

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 very short (two sentences), but not overly verbose. However, it lacks crucial details, so conciseness comes at the expense of informativeness.

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?

With no output schema, no annotations, and three unelaborated parameters, the description is incomplete. It covers destructive nature but omits parameter meanings, return values, and behavior details.

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 description does not explain any of the three parameters (env_id, dry_run, agent_token) beyond a brief mention of dry_run. Schema description coverage is 0%, so the description fails to compensate.

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?

Clearly states it prunes unused Docker volumes, with a specific verb and resource. Distinguishes from sibling tools like remove_volume (targeted removal) and prune_system (broader scope).

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?

Provides minimal guidance about using dry_run first, but does not compare this tool to alternatives like remove_volume or prune_system, nor specify when to use it.

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