delete_namespace

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

With no annotations provided, the description clearly labels the tool as 'DESTRUCTIVE' and 'irreversible', and lists the types of resources that will be permanently deleted (pods, services, PVCs, etc.). This provides good behavioral transparency.

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: a warning header, irreversibility note, a list of affected resources, and the two parameters. Every sentence is necessary and front-loaded with the important destructive warning.

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?

The description adequately covers the destructive nature and consequences of the operation. Given that an output schema exists, the lack of return value details is acceptable. The description is complete for a tool with this level of complexity.

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 description adds meaning to the parameters: 'name: Namespace to delete.' and 'cluster: Named cluster to target (empty = default).' This clarifies the purpose and default behavior, which is useful since the schema has 0% coverage.

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 'Delete a namespace and ALL resources within it.', specifying the verb 'delete' and the resource 'namespace'. This distinguishes it from siblings like 'create_namespace' or 'list_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?

The description warns about irreversibility but does not provide explicit guidance on when to use this tool versus alternatives such as 'delete_resource'. The usage context is implied but lacks direct comparative guidance.

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