IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating it's not a read-only operation, but the description doesn't add behavioral context beyond that. It doesn't explain what 'calculate' entails (e.g., whether it performs computations without side effects, returns structured data, or has rate limits). Since annotations cover basic safety, the description adds minimal value, scoring baseline for adequate but not rich disclosure.

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, efficient sentence with no wasted words. It's front-loaded with the core action ('calculate') and resource ('IPv6 subnet information'), making it easy to parse. Every word contributes directly to stating the tool's purpose, exemplifying optimal conciseness.

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 and minimal annotations, the description is adequate but incomplete. It specifies what's calculated but not the output format (e.g., network address, broadcast, range). With 100% schema coverage for inputs, it meets minimum viability but lacks details on results or error handling, making it functional but not fully informative.

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%, with clear descriptions for both parameters (e.g., 'IPv6 address and prefix' and 'New prefix length for subnetting'). The description doesn't add meaning beyond the schema, such as explaining subnetting concepts or format examples. Given high schema coverage, baseline 3 is appropriate as the schema handles parameter documentation adequately.

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 verb 'calculate' and the resource 'IPv6 subnet information', making the purpose evident. However, it doesn't differentiate from sibling tools like 'calculate_ip_subnet' or 'calculate_ipv4_subnet', which would require specifying it's specifically for IPv6 addresses. The title 'Ipv6-subnet-calculator' in annotations reinforces this, but the description itself lacks explicit distinction.

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 sibling tools like 'calculate_ip_subnet' and 'calculate_ipv4_subnet', it's unclear if this is for IPv6-specific calculations or a general tool that handles IPv6. No context, exclusions, or prerequisites are mentioned, leaving usage ambiguous.

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