remove_ip_pool

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

While annotations already mark the operation as destructive and idempotent, the description adds meaningful behavioral context by noting the failure condition when the pool is in use. It also clarifies the target environment (MikroTik device). This goes beyond the structured annotations and provides an important edge case for the agent to consider.

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 a single concise sentence that conveys the core action and a key constraint. It is front-loaded with the verb and resource, contains no filler, and is easy to parse at a glance.

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?

Despite its brevity, the description covers the essential behavior (removing an IP pool) and the most important caveat (fails if in use). The existence of an output schema likely covers return values, and the two parameters are simple enough that their roles are somewhat inferable. However, the lack of guidance on the 'device' parameter and when to use the tool relative to alternatives leaves a minor gap.

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?

Schema description coverage is 0%, so the description must compensate for parameter meanings, but it does not. It does not explain that 'name' identifies the IP pool or clarify the role of the optional 'device' parameter. The description only says 'an IP pool' generically, leaving the agent to infer the mapping between arguments and their semantics.

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 the action ('Removes an IP pool') and the target resource ('from the MikroTik device'), making it obvious that this tool deletes IP pools. It is distinct from sibling tools like remove_ip_address or remove_dhcp_server, and the name aligns perfectly with the described behavior.

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 phrase 'fails if pool is in use' implies a precondition for use, suggesting that users should not attempt removal when the pool is active. However, it does not explicitly state when to use the tool or mention alternatives like checking usage via list_ip_pool_used or updating the pool instead. The usage context is implied rather than stated.

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