ssh_session_command

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

No annotations provided, so description carries full burden. Discloses timeout default but omits behavioral details: whether command is blocking, stderr handling, error states (timeout, failed session), or if output is streaming or batched. Insufficient for a command execution tool.

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?

Highly concise: one-line purpose, Args/Returns sections. No redundant information. Every sentence serves a purpose.

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 no annotations and only 3 parameters, description lacks context on error handling, synchronous vs asynchronous nature, or relation to other exec tools (e.g., exec_stream). Does not confirm return format beyond 'Command output.' Output schema exists but is not referenced.

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 0%, requiring description to explain parameters. Lists three parameters with brief explanations (e.g., 'session_id: The SSH session ID'), adding some value but mostly restating parameter names. Timeout includes default, which is helpful. Does not provide format constraints or example values.

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 'Execute a command in an active SSH session,' specifying verb and resource. It distinguishes from sibling session management tools (start/stop/upload) but does not differentiate from other command execution tools like msf_session_execute or reverse_shell_command.

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?

No explicit when-to-use or when-not-to-use guidance. Implies usage for active SSH sessions but does not mention prerequisites (e.g., session must be started) or alternatives among sibling tools.

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