delete_ip_pool

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

Describes the irreversible nature, rejection conditions, and return format (confirmation string or error string), going beyond annotations which only mark as destructive.

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?

Highly concise yet comprehensive: header, warning, usage steps, parameter descriptions, all in a clear structure 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?

Fully covers the operation's purpose, prerequisites, behavior, and output, making it complete for an AI 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?

With 0% schema coverage, the description adds crucial meaning: pool_id is from list_ip_pools, target is optional defaulting from config.

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 the action 'Permanently delete an IP address pool' with a [WRITE] tag, clearly differentiating from sibling tools like list_ip_pools and get_ip_pool_usage.

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 when-to-use (to delete a pool) and when-not-to-use (if active allocations exist), and recommends checking usage first via get_ip_pool_usage, plus user confirmation.

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