delete_pv

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

With no annotations, the description carries the full burden. It warns about potential issue if PVC is bound but does not describe what happens on deletion (e.g., error, destruction, cascade), nor does it mention auth requirements or idempotency.

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 extremely concise, with one sentence and a warning. It is front-loaded and every part adds value.

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?

Despite simplicity, the description lacks details on return values, prerequisites beyond the warning, and how to verify precondition. The warning is helpful but incomplete for a safe deletion operation.

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 description coverage is 0%, and the description adds no explanation for either parameter ('name' or 'cluster'). The agent must infer their usage from names alone.

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 'Delete a PersistentVolume' clearly states the verb and resource. The warning about ensuring no PVC is bound further clarifies the scope and distinguishes it from related tools like delete_pvc.

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 warning provides a precondition ('ensure no PVC is bound'), giving some usage guidance. However, it does not specify when to use or avoid this tool, nor does it mention alternatives like checking PVCs first.

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