delete_pvc

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

Warns about potential data loss if PVC is in use, which is a key behavioral trait. However, with no annotations, more details (e.g., irreversible deletion, permission requirements) would improve transparency. The warning adds some value.

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?

Extremely concise: one sentence with a critical warning. No unnecessary words. Front-loaded with the core action.

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?

For a destructive tool with 3 parameters and an output schema, the description lacks details on parameter usage, output, and prerequisites. Among many sibling tools, it does not help differentiate usage.

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%, but the description does not explain any parameter. It does not clarify what 'name', 'cluster', or 'namespace' represent, nor their defaults or constraints.

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 the action 'Delete' and the resource 'PersistentVolumeClaim'. Distinguishes from siblings like delete_pv (different resource) and create_pvc (opposite operation).

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 explicit guidance on when to use this tool vs alternatives. The warning about data loss implies caution but does not specify prerequisites or conditions for safe usage.

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