MCP SSH Manager

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. While 'manage' implies mutation capabilities, it doesn't specify permission requirements, whether operations are reversible, error handling behavior, or what the tool returns. For a multi-action tool with create/update/delete operations, this minimal description leaves critical behavioral aspects undocumented.

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 extremely concise (7 words) and front-loaded with the core purpose. Every word earns its place, though it could benefit from slightly more detail given the tool's complexity. The structure is clear but minimalistic.

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 multi-action tool with 7 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't explain what constitutes a 'server group', how actions differ, what the tool returns, or error conditions. The description fails to compensate for the lack of structured behavioral information, leaving significant gaps for agent understanding.

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 schema has 100% description coverage, so all parameters are documented in the structured schema. The description adds no parameter-specific information beyond implying that 'server groups' are the resource being managed. It doesn't explain relationships between parameters (e.g., which parameters apply to which actions) or provide usage examples. Baseline 3 is appropriate when 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 verb ('manage') and resource ('server groups') with specific operations enumerated (create, update, delete, list). It distinguishes this tool from siblings like ssh_list_servers or ssh_execute_group by focusing on group management rather than server listing or command execution. However, it doesn't explicitly mention the additional actions (add-servers, remove-servers) shown in the schema.

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 prerequisites, differentiate from similar tools like ssh_execute_group (which executes commands on groups), or specify when certain actions are appropriate. With 35 sibling tools in the SSH domain, this lack of contextual guidance is a significant gap.

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