MCP SSH Orchestrator

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers only 'Health check' - no information about whether this is a read-only operation, what permissions it requires, whether it makes network connections, what happens on failure, or what the typical response looks like. For a tool that presumably tests SSH connectivity or service health, this lack of behavioral context is a significant gap.

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?

While technically concise with just two words, this represents under-specification rather than effective brevity. The description fails to convey essential information that would help an agent understand and use the tool correctly. Every sentence should earn its place, but here the minimal content doesn't earn its place by providing sufficient value to the agent.

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 that this is a health check tool with no annotations, the description is incomplete despite the existence of an output schema. The agent needs to understand what 'health' means in this context, what systems are being checked, and what the typical use cases are. With sibling tools for running commands, managing hosts, and handling tasks, this tool's specific role remains unclear. The output schema helps with interpreting results but doesn't compensate for the inadequate functional description.

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 tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation (none). The description doesn't need to compensate for any parameter documentation gaps. While it could theoretically mention that no parameters are required, the baseline for zero-parameter tools with complete schema coverage is appropriately a 4, as there's no parameter semantics burden to address.

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 'Health check' is vague and tautological - it essentially restates the tool name 'ssh_ping' without specifying what resource or system is being checked. It doesn't distinguish this from potential sibling health-check tools or explain what 'ping' means in this SSH context. While better than a single word like 'Process', it provides minimal actionable information about the tool's actual function.

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 absolutely no guidance on when to use this tool versus alternatives. With sibling tools like ssh_describe_host, ssh_list_hosts, ssh_run, and various task management tools, there's no indication whether this is for connection testing, service availability checking, or general system health assessment. The agent receives no help in selecting this tool over other SSH-related options.

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