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 but only states 'tail remote log files in real-time.' It lacks critical behavioral details: whether this opens a persistent connection, requires specific permissions, has rate limits, what happens on errors, or the output format (e.g., streaming vs. batch). For a real-time tool with zero annotation coverage, this is insufficient.

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 waste. It's front-loaded with the core purpose and uses precise language, making it easy for an agent to parse quickly.

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 real-time monitoring tool with no annotations and no output schema, the description is incomplete. It misses behavioral context (e.g., connection handling, streaming behavior), error handling, and output details. Given the complexity and lack of structured data, more guidance is needed for safe and effective use.

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%, providing clear documentation for all 5 parameters. The description adds no parameter-specific information beyond implying real-time tailing, which aligns with the 'follow' parameter. Baseline 3 is appropriate as the schema adequately covers parameter semantics.

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 ('tail') and resource ('remote log files') with the qualifier 'in real-time' indicating streaming behavior. It distinguishes from siblings like ssh_execute or ssh_download by focusing specifically on log monitoring, though it doesn't explicitly contrast with similar tools like ssh_monitor.

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?

No guidance on when to use this tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., SSH configuration), exclusions, or comparisons to siblings like ssh_monitor or ssh_execute with tail commands, leaving the agent to infer usage context.

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