range_to_cidrs

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

With no annotations, the description carries the burden. It truthfully states the conversion to a 'minimal list of covering CIDRs', but does not disclose input validation, handling of invalid IPs, or whether it supports IPv6. The simplicity reduces the need for more, but some gaps remain.

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, well-structured sentence with no unnecessary words. It conveys the core functionality efficiently.

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's low complexity and lack of output schema, the description sufficiently explains what the tool does and what it returns (a list of CIDRs). However, it omits error handling and specific IP format requirements, which are minor gaps.

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%, yet the description does not elaborate on the parameters. It only names them implicitly ('first_ip', 'last_ip') but provides no format guidance (e.g., dotted decimal, CIDR notation) or constraints. This is insufficient for a tool requiring valid IP addresses.

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 ('convert') and the resource ('inclusive IP address range' to 'minimal list of covering CIDRs'). It is specific and distinguishes well from sibling tools like cidr_to_range (reverse operation) and check_coverage.

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 implies when to use this tool (when you have an IP range and need CIDR representation) but does not explicitly mention when not to use it or suggest alternatives. Sibling tool names hint at other operations, but no direct guidance is provided.

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