delete_ip_pool

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

Annotations already give destructiveHint=true, but the description adds irreversible consequences, impact on consumers, error conditions, audit logging, return format, and connectivity failure. No contradiction with annotations.

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 well-structured with a [WRITE] label, main action, implications, usage guidance, and clear Args section. Every sentence is meaningful with no 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 complexity (destructive, with prerequisites and error handling) and presence of annotations and output schema, the description is fully complete: it covers behavior, prerequisites, error cases, return format, audit logging, and parameter details.

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?

With 0% schema description coverage, the description provides full parameter semantics: pool_id is the ID from list_ip_pools, target is the NSX Manager name from config.yaml with default behavior. This compensates completely.

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 'Permanently delete an IP address pool' with a [WRITE] prefix, specifying the exact action and resource. It distinguishes itself from sibling tools like create_ip_pool and list_ip_pools.

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?

Explicitly provides a prerequisite workflow: run list_ip_pools and get_ip_pool_usage first to confirm the pool is unused, and confirm with the user. It also explains when deletion is rejected (active allocations).

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