MCP SSH Manager

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions sudo execution but doesn't describe critical behaviors: whether it requires pre-configured SSH access, what happens on authentication failure, how output is returned, or error handling. The password masking note is in the schema, not the description. For a privileged execution tool with zero annotation coverage, this leaves significant gaps.

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 that states the core functionality without unnecessary words. It's appropriately sized for a straightforward tool and front-loads the essential information ('Execute command with sudo').

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 complexity of privileged remote execution with 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what the tool returns (e.g., stdout/stderr, exit codes), error conditions, security implications, or dependencies on SSH configuration. For a tool with this level of responsibility, more context is needed.

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%, so the schema fully documents all 5 parameters. The description adds no additional parameter semantics beyond implying 'command' is executed with sudo privileges. Since the schema does the heavy lifting, the baseline score of 3 is appropriate, though the description provides minimal value over the structured data.

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 action ('Execute command') and target ('on remote server') with the specific method 'with sudo'. It distinguishes from sibling tools like 'ssh_execute' by specifying the sudo privilege requirement. However, it doesn't explicitly mention how it differs from other sudo-related tools that might exist in the sibling 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 sudo is required versus using 'ssh_execute', nor does it reference any of the many sibling tools for context-specific alternatives. The agent must infer usage from the name alone.

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