create_ip_pool

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

Annotations show readOnlyHint=false (write operation), destructiveHint=false. The description adds that it is a PUT-like operation that overwrites on same pool_id, returns a dict or error, and requires IPs to be inside cidr. It also references verification and inverse tools. This adds meaningful context beyond 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 clear summary, contextual notes, and parameter details. It front-loads the purpose. While not overly verbose, it could be slightly more concise, but the organization and readability are good.

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 has 7 parameters (5 required), no output schema, and multiple sibling tools, the description covers prerequisites (list_ip_pools), overwrite behavior, return format (dict or error), and parameter constraints. It also suggests verification. This is fairly complete for agent decision-making.

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 carries full burden. It provides an Args section explaining each parameter: pool_id (uniqueness, path), display_name (UI), start_ip and end_ip (examples), cidr (subnet), gateway_ip (optional, example), target (optional, default). This adds essential meaning beyond the schema's bare names and types.

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] Create an IP address pool with one static subnet and allocation range', clearly stating the verb (create) and resource (IP pool). It distinguishes from sibling tools like list_ip_pools, get_ip_pool_usage, and delete_ip_pool by mentioning them in context.

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 advises to run list_ip_pools first to avoid overlapping ranges, and suggests verifying with get_ip_pool_usage. It notes the inverse operation (delete_ip_pool) and warns about the overwrite behavior when the same pool_id is used. It does not explicitly state when not to use, but provides good contextual guidance.

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