k8s_delete_ns

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

Discloses destructive behavior ('delete and all resources within it') and lists protected namespaces. Without annotations, this adds good transparency despite lacking details on side effects like irreversibility.

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 sentences, each earning its place: first states action, second adds critical constraint. 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?

Covers the main purpose and protection list. For a destructive tool with two params, it is fairly complete, though parameter documentation is missing.

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?

Description does not explain the two parameters (name, context). With 0% schema coverage, the description fails to compensate, leaving the agent without guidance on parameter values.

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 a Kubernetes namespace and all resources within it. Distinguishes itself from other delete tools by focusing on namespace-level deletion and mentions protected namespaces.

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?

Lists protected namespaces that cannot be deleted, providing clear when-not-to-use context. However, does not explicitly compare with sibling tools like k8s_delete_resource.

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