k8s_delete_resource

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

No annotations provided; description discloses force/grace_period but lacks details on cascading effects, blocking behavior, or destructive nature.

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?

Two concise sentences, front-loaded with action, no unnecessary words.

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 complex Kubernetes tool with 6 parameters and no output schema, the description is sparse; does not explain how namespace interacts with resource_type or specify return behavior.

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 has 0% description coverage; description only explains force and grace_period relationship, leaving name, context, namespace, and resource_type undocumented.

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 deletes Kubernetes resources and lists many common resource types, distinguishing it from create/apply tools.

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 guidance on force=true for immediate deletion but does not explicitly tell when to use this tool vs other deletion tools like k8s_delete_ns.

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