IT Tools MCP Server

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

Annotations provide readOnlyHint=false (implying potential mutation, though this seems contradictory for a calculation tool) and a title. The description adds no behavioral context beyond the basic purpose - no information about what specific subnet information is returned, error conditions, performance characteristics, or authentication needs. However, it doesn't contradict the 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 extremely concise - a single 5-word phrase that gets straight to the point. There's zero wasted language or unnecessary elaboration. It's appropriately sized for a straightforward calculation tool.

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?

For a calculation tool with no output schema, the description is insufficient. It doesn't explain what subnet information is calculated (network address, broadcast address, subnet mask, usable IP range, etc.). With no annotations covering output behavior and no output schema, the description should provide more context about what the tool actually returns.

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 100% schema description coverage, both parameters (ip and cidr) are well-documented in the schema with examples. The description adds no additional parameter semantics beyond what's already in the schema. The baseline score of 3 is appropriate when the schema does the heavy lifting.

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 'Calculate subnet information for IPv4' states the general purpose (calculate subnet info) and resource (IPv4), but it's vague about what specific information is calculated. It doesn't distinguish from sibling tools like 'calculate_ipv4_subnet' which appears to be a near-duplicate, or 'convert_cidr_to_ip_range' which might provide overlapping functionality.

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 provides no guidance on when to use this tool versus alternatives. With multiple sibling tools related to IP/subnet calculations (calculate_ipv4_subnet, calculate_ipv6_subnet, convert_cidr_to_ip_range, convert_ip_range_to_cidr), there's no indication of which tool to choose for what specific subnet calculation needs.

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