execute_ssh

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

With no annotations, the description carries the full burden, yet it omits that this runs arbitrary commands with remote execution power (effectively destructive), how authentication is established, whether sudo is available, or any timeout/rate behavior. 'Legacy compatibility' hints at deprecation status but is left unexplained.

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?

One short sentence with no padding, and the legacy/deprecation caveat is front-loaded. It is perhaps too terse for a tool that executes arbitrary remote commands, but there is no wasted text.

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?

An output schema exists, so return values need not be explained. But for an SSH execution tool in a family with credential setup, sudo, and duplicate execute variants, the description says nothing about auth prerequisites, privilege level, or why a near-identical sibling exists — key gaps an agent needs resolved before 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 description coverage is 0%, so the description must compensate; it only restates the two parameter names via 'command' and 'remote Linux host'. It does not specify hostname format (IP vs. FQDN, user@host?) or whether the command is run through a shell, which matters for quoting and multi-command strings.

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?

Specific verb + resource: 'Execute command on remote Linux host via SSH', which tells the agent exactly what happens. However, it does not differentiate from the near-identical siblings ssh_execute_ssh and execute_sudo, so an agent still cannot tell which of the three to pick from the description alone.

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 prefix 'Legacy compatibility' weakly implies a preference for other tools, but no alternative is named and no condition for choosing this over ssh_execute_ssh, ssh_execute_sudo, or execute_sudo is given. No prerequisites (e.g., credentials must be set up first via ssh_setup_credentials) are mentioned.

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