delete_namespace

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

Beyond annotations (destructiveHint=true), the description adds important behavioral details: it is a write operation, rejects deletion when TKC clusters exist, and dry_run is a safety mechanism defaulting to true. This adds context about execution behavior and safety constraints.

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 concise and well-structured: a title line, safety note, important note with defaults, and a list of parameter details. Every sentence adds value without redundancy.

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?

Given the tool's complexity (4 parameters, no output schema), the description covers essential behavioral aspects: safety checks, parameter roles, and execution flow. It could mention the response or side effects, but it is largely sufficient for an agent to use correctly.

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 explains three of four parameters (name, confirmed, dry_run) with meanings and default behaviors. However, the 'target' parameter is not mentioned at all. Schema description coverage is 0%, so the description partially compensates but leaves a gap.

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 explicitly states 'Delete a vSphere Namespace' with a [WRITE] tag. It distinguishes itself from siblings like create_namespace, update_namespace, and get_namespace. The verb and resource are clear and specific.

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 usage guidance: it states that deletion is rejected if TKC clusters exist and instructs to delete them first. It also explains that dry_run=True by default and that confirmed=True is required to proceed. It lacks explicit when-not-to-use instructions but adequately covers prerequisites and execution steps.

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