delete_namespace

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds critical safety behavior: rejection when TKC clusters exist, and the need for both dry_run=False and confirmed=True. This goes beyond annotations, but missing details on error handling or idempotency.

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?

Very concise: 6 sentences covering action, safety, important flags, and parameter list. Uses clear formatting with [WRITE], SAFETY, IMPORTANT sections. 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 essential behavioral context for a delete operation: preconditions (no TKC clusters), safety gates (confirmed, dry_run). No output schema, so the description should mention return value or error behavior, which is absent. Still, it provides enough for correct usage.

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 explains name, confirmed, and dry_run including their defaults and role in the safety gate. The 'target' parameter is not mentioned. Schema has 0% coverage, so the description adds substantial meaning for 3 of 4 parameters.

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 starts with '[WRITE] Delete a vSphere Namespace,' clearly stating the action and resource. It is distinct from sibling tools like create_namespace, update_namespace, and 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?

Provides explicit safety condition: 'Rejects if TKC clusters exist inside. Delete TKC clusters first.' Also explains required flags: 'dry_run=True by default — set dry_run=False AND confirmed=True to delete.' This guides the agent on preconditions and correct invocation, though it does not explicitly contrast with delete_tkc_cluster.

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