IT Tools MCP Server

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

Annotations provide readOnlyHint=false, indicating a write/mutation operation, but the description adds no behavioral context beyond the basic action. It doesn't specify what 'test' entails (e.g., connection attempt timeout, success/failure output), rate limits, or side effects (e.g., network traffic generation). With annotations covering the safety hint, a baseline 3 is appropriate as the description adds minimal value.

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 zero wasted words. It front-loads the core action ('Test TCP connectivity') and immediately specifies the target, making it highly scannable and appropriately sized for a simple 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 simple connectivity tool with two well-documented parameters and annotations, the description is minimally adequate. However, it lacks output details (no schema provided) and behavioral nuances (e.g., what constitutes a successful test), leaving gaps in full contextual understanding. It meets the baseline but doesn't excel.

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 connect to', 'Port number'). The description adds no additional semantic context beyond implying these parameters are used for the connectivity test. Since the schema does the heavy lifting, the baseline score of 3 is warranted.

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 specific action ('Test TCP connectivity') and target ('to a host and port'), using precise technical terminology. It distinguishes itself from sibling tools like 'ping' (which tests ICMP connectivity) and 'curl' (which performs HTTP requests), establishing a clear, distinct purpose.

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 'ping' (for ICMP) or 'curl' (for HTTP). It lacks any mention of prerequisites, typical use cases (e.g., troubleshooting network services), or exclusions (e.g., not for encrypted connections), leaving the agent with no contextual usage cues.

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