k8s_delete_namespace

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It effectively communicates the destructive nature of the operation ('WARNING: This will delete all resources in the namespace'), which is crucial for a deletion tool. However, it doesn't mention other behavioral aspects like permissions required, whether the operation is reversible, or error conditions.

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 just one sentence that front-loads the core action and includes a critical warning. Every word earns its place, with no redundant information or unnecessary elaboration.

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 no annotations and no output schema, the description does well by emphasizing the dangerous nature of the operation. However, it could be more complete by mentioning prerequisites (like needing appropriate permissions) or what happens after deletion (e.g., whether the namespace name becomes available for reuse).

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 input schema has 100% description coverage, with the single parameter 'name' clearly documented as 'Namespace name to delete'. The description doesn't add any additional parameter information beyond what's in the schema, so it meets the baseline expectation when schema coverage is complete.

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 clearly states the action ('Delete a namespace') and specifies the target resource ('namespace'), making the purpose immediately apparent. It distinguishes itself from sibling tools like 'k8s_delete_pod' or 'k8s_delete_resource' by focusing specifically on namespace deletion rather than other resource types.

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 description provides clear context for when to use this tool through the WARNING about deleting all resources in the namespace, which implicitly suggests it should be used with caution for destructive operations. However, it doesn't explicitly mention when NOT to use it or name specific alternatives like 'k8s_list_namespaces' for checking namespace existence first.

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