IT Tools MCP Server

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

Annotations indicate readOnlyHint=false, which aligns with the description's 'Connect' action (implying potential write operations via the command parameter). The description adds minimal behavioral context beyond annotations—it doesn't specify what happens during connection (e.g., interactive session, command execution, error handling) or security implications. No contradiction with annotations exists.

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's front-loaded with the core action and resource, making it immediately scannable and appropriately sized for a tool with clear parameters in the schema.

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?

Given the tool's complexity (SSH connection with command execution) and lack of output schema, the description is minimally adequate. It covers the basic action but lacks details on return values, error conditions, or behavioral specifics. With annotations providing only readOnlyHint, more context on security or session management would improve completeness.

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, all parameters are documented in the schema. The description adds no additional semantic context about parameters beyond implying SSH connection. It doesn't explain parameter relationships (e.g., how privateKey interacts with authentication) or usage nuances, 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 'Connect to a target via SSH' clearly states the verb ('Connect') and resource ('target via SSH'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'telnet' or 'scp' by specifying SSH protocol, though it doesn't explicitly differentiate from all network/remote tools in the list.

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. It doesn't mention when SSH is preferred over other remote access tools like 'telnet' or file transfer tools like 'scp', nor does it specify prerequisites or typical use cases beyond the basic connection statement.

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