ssh_execute

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

Discloses mutates remote state, alias expansion, OS syntax adaptation, timeout behavior, mode restrictions, and output truncation. No annotations provided, so description fully bears the burden.

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?

Every sentence adds unique information. Front-loaded with core purpose, followed by essential behavioral details. No redundancy.

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?

Explains return values (stdout, stderr, exit code), conditions, and all parameter behaviors. Adequate despite no output schema.

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 covers all 4 parameters (100% coverage). Description adds value by explaining cwd fallback, timeout default/max, and alias expansion context beyond schema descriptions.

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?

Clearly states 'Runs a shell command over SSH on a named configured server and returns stdout, stderr, and exit code.' This is a specific verb+resource. Distinguishes from siblings like ssh_execute_group and ssh_execute_sudo by focusing on basic execution.

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?

Provides context on readonly/restricted modes, timeout limits, and aliases. Does not explicitly name alternatives, but the behavior details help agents decide when to use this tool.

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