execute

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

No annotations are provided, so the description carries the burden. It discloses the core behavior (executing a command), the return format (stdout/stderr and exit status), and default timeout. However, it does not warn about potential destructive side effects or prerequisites like an active session, which is a significant gap for an 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?

The description is efficiently structured as a docstring with Args and Returns sections. Every line adds value, with no redundant information and clear separation of parameter details.

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?

Covers the tool's purpose, parameters, and return value well. Missing usage prerequisites (e.g., active session) and safety warnings, but for a straightforward execution tool with a simple schema, it is largely complete.

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?

Input schema has 0% description coverage, so the description fully compensates by explaining all four parameters with purpose and defaults. It adds meaningful context like 'input string to provide' and 'timeout in seconds' beyond what the schema offers.

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 states 'Execute command on SSH server' with a specific verb and resource. Clearly distinguishes from sibling tools like connect, disconnect, upload, and download, which handle session management and file transfer.

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 clearly implies when to use this tool: when you need to run a command on an existing SSH session. It provides concrete context (session_id, command, timeout) but does not explicitly exclude alternatives or mention when not to use it.

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