Run a shell command on the remote host

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

With no annotations, the description carries the full transparency burden. It explicitly warns that 'destructive operations are NOT blocked by this server', clearly disclosing the risk. However, it does not mention return values, error behavior, or success/failure indicators.

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: two sentences that directly state the purpose and a critical warning. No superfluous words, front-loaded with the core action.

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 5 parameters, no output schema, and no annotations, the description should provide more context about what the tool returns, error handling, or when to use specific parameters (e.g., cwd, stdin). The existing warning is important but insufficient for full usability.

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 80%, so most parameters are already explained in the schema. The description adds minimal additional meaning beyond the schema details (e.g., no new context for parameters).

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 'Execute a shell command over SSH on the named connection', specifying the action, protocol, and target. It directly matches the tool name 'exec' and its title, and is distinguishable from siblings like 'exec_as' or 'exec_start' which have different scopes.

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 includes a strong warning about destructive operations and the responsibility of the MCP client, but does not provide explicit guidance on when to use this tool versus its siblings (e.g., exec_as for a different user, exec_start for background).

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