ssh_execute_command

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

Annotations set destructiveHint=false and readOnlyHint=false, but the description explains auto-injection of credentials and a recovery path for missing credentials. However, it does not disclose that arbitrary commands could be destructive, which is a notable omission given the openWorldHint=true.

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 three sentences, each adding essential information: purpose, credential handling, and failure recovery. No redundant or unnecessary content.

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?

The tool has no output schema, so the description should clarify expected output (e.g., stdout/stderr/exit code). While annotations provide some context, the description omits what the agent should expect as a result of execution.

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 100%, so the baseline is 3. The description adds value by explaining the auto-injection behavior for username/password and tying it to the keyring workflow, which goes beyond the 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?

The description clearly states the tool executes a command on a remote system via SSH, which is a specific verb-resource combination. It distinguishes itself from sibling tools like ssh_discover and start_interactive_shell by focusing on command 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?

The description provides explicit guidance on when to omit username/password (if stored in keyring) and what to do if authentication fails ('run `homelab-mcp credentials add`' or call `list_keyring_credentials`). It does not, however, compare directly to alternatives like start_interactive_shell, leaving some ambiguity.

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