ssh_exec

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

No annotations provided, so description must disclose behavior. It mentions outputs but omits critical traits: commands can be destructive, no readOnlyHint, no mention of side effects or security restrictions.

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?

Two short sentences: first defines purpose, second defines outputs. No fluff, front-loaded with key information.

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?

For an exec tool with no output schema and no annotations, the description is too sparse. Missing usage context, error handling, relation to sibling sesstools (ssh_sudo_exec), and safety warnings. Incomplete for a potentially destructive operation.

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 has 100% parameter description coverage. The description adds value by stating return format (stdout, stderr, exit code) which is not in schema. This elevates it slightly above baseline 3.

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?

Description clearly states verb 'Execute' and resource 'command on remote server via SSH', with output detail (stdout, stderr, exit code). Sibling 'ssh_sudo_exec' is distinct, so this is well-differentiated.

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?

Description does not specify when to use this tool (e.g., need an active session from ssh_connect) or when alternatives like ssh_sudo_exec are appropriate. No guidance on prerequisites or context.

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