IT Tools MCP Server

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

Annotations provide readOnlyHint=false (indicating potential side effects), but the description doesn't add behavioral context beyond the example. It doesn't mention what the tool actually does (e.g., sends ICMP packets, measures latency, returns success/failure), potential network impacts, or output format. With annotations covering the safety hint, the description adds minimal value but lacks rich behavioral 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 perfectly concise with two sentences: one stating the purpose and one providing an example. It's front-loaded with the core function and wastes no words, making it easy for an agent to quickly understand the tool's intent.

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 network testing tool with 2 parameters (100% schema coverage) and readOnlyHint=false annotation, the description is adequate but incomplete. It lacks details on output (no output schema), error handling, or network-specific behaviors (e.g., timeout, packet size). The example helps, but more context would improve agent understanding given the tool's functional complexity.

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 parameter descriptions ('Host to ping', 'Number of ping attempts'). The description doesn't add any parameter semantics beyond what the schema provides, such as explaining valid target formats (hostname vs. IP) or count limitations. Baseline 3 is appropriate since 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 clearly states the tool's purpose with a specific verb ('Test network connectivity') and resource ('to a host'), and includes a concrete example ('ping google.com'). It effectively distinguishes this network testing tool from sibling tools that perform text analysis, calculations, conversions, or other operations.

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 an example ('ping google.com to check if it's reachable') that implies usage for network reachability testing, but it doesn't explicitly state when to use this tool versus alternatives like 'curl', 'dig', 'nslookup', or 'telnet' (which are sibling tools on this server). The guidance is helpful but not comprehensive about tool selection.

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