IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating this isn't a read-only operation, but the description doesn't add meaningful behavioral context beyond that. It doesn't explain what 'calculate' entails (e.g., computational vs. network operation), error conditions, or performance characteristics. With annotations covering the basic safety profile, the description adds minimal value but no contradictions.

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 perfectly concise at just four words ('Calculate IPv4 subnet information'), front-loading the essential purpose with zero wasted words. Every element earns its place, making it efficient for an agent to parse.

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 single-parameter tool with good schema coverage but no output schema, the description is minimally adequate. It states what the tool does but lacks details on return values, error handling, or examples that would help an agent understand the full context of use.

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?

The input schema has 100% description coverage, with the single parameter 'cidr' well-documented as 'IPv4 CIDR notation (e.g., 192.168.1.0/24)'. The description doesn't add any parameter semantics beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 IPv4 subnet information' clearly states the verb ('calculate') and resource ('IPv4 subnet information'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from its sibling 'calculate_ip_subnet' or 'calculate_ipv6_subnet', which would be needed for a perfect score.

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 like 'calculate_ip_subnet' or 'convert_cidr_to_ip_range'. There's no mention of prerequisites, typical use cases, or comparison with sibling tools, leaving the agent without contextual usage information.

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