network_subnet_calculator

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

Annotations already mark the tool as readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds crucial context: 'Pure offline IPv4 math: read-only, non-destructive, contacts no DNS or network service, and is rate-limited (30 requests/minute for anonymous callers).' This enhances transparency beyond annotations. No contradiction.

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 paragraph that efficiently conveys the purpose, use cases, behavior, and limitations. It is well-structured, front-loading the core purpose and output list, then providing usage guidance and behavioral notes. No unnecessary words.

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 6 parameters (0 required), 100% schema coverage, and an output schema, the description covers all essential aspects: purpose, input modes, output fields, behavioral guarantees (offline, read-only, rate-limited), and differentiation from siblings. It does not need to explain return values since an output schema exists.

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 100%, so baseline is 3. The description adds context about when each parameter is used (e.g., 'Used when inputFormat is cidr') and explains the purpose of the input modes. While the schema already documents each parameter, the description clarifies the conditional relationships, justifying a slightly higher score.

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 it is an IPv4 Subnet Calculator, specifies the two input modes (CIDR or IP+Mask), and lists the computed outputs. It also distinguishes itself from sibling tools like network_cidr_calculator and network_ip_range_calculator by stating their different purposes.

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 explicitly tells when to use this tool (compute subnet details) and when not to (for conversion or enumeration, directing to siblings). It also mentions the tool is pure offline math and read-only, setting appropriate expectations.

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