mcp_ssh_manager

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

The description discloses key behaviors: data encryption for credentials, sequential per-profile execution, and no concurrency. With no annotations provided, this is adequate but lacks details on error handling, return values, or auth requirements.

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 relatively concise but poorly structured, appearing as a run-on sentence listing actions. It could be improved with bullet points or clearer separation of action descriptions.

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 (11 parameters, no output schema), the description lacks essential details about host/port/timeout parameters and return values. It covers actions but not the full parameter context needed for correct invocation.

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 coverage is low (18%). The description adds meaning for a few parameters (password, private_key, passphrase in setup_profile) but fails to describe host, port, username, timeouts, etc. It does not sufficiently compensate for the low 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 clearly states it is an 'SSH executor' and lists specific actions (setup_profile, list_profiles, execute, system_info, check_host), distinguishing it from sibling tools mcp_api_client and mcp_psql_manager which serve different purposes.

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 clear context for each action, including constraints like sequential execution and no concurrent runs. However, it does not explicitly state when to use this tool versus alternatives or when not to use it.

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