execute_command

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

With no annotations provided, the description carries the full burden and does an excellent job. It discloses automatic async transition after timeout, automatic sudo prefixing, enable mode entry, session persistence, interactive input support, and command interruption. All these are behavioral traits beyond the input schema and are highly relevant for safe and correct invocation.

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 well-structured with a front-loaded summary, detailed paragraphs, and a bulleted 'Advanced Features' list. It is somewhat long but every section adds necessary detail for a tool with 10 parameters. Minor redundancy exists between the initial paragraphs and the advanced features list, but overall it is appropriately sized and organized.

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 description is comprehensive for a complex tool: it covers all parameters, device-specific behaviors, timeout handling, and advanced features. An output schema exists, so return value details are not required. Given no annotations and high complexity, the description fully equips an agent to use the tool correctly.

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?

The schema provides 0% description coverage for parameters, but the description lists all 10 parameters with clear meanings, defaults, and examples (e.g., host as 'myserver', timeout default 30). It adds substantial value beyond the bare schema, fully compensating for the lack of schema-level 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 'Execute a command on an SSH host using a persistent session', which is a specific verb+resource. It distinguishes itself from the sibling execute_command_async by explaining the synchronous start and async transition behavior, making its unique role clear.

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 usage context for different scenarios: using enable_password for network devices, sudo_password for Unix/Linux hosts, and handling SSH config aliases. It does not explicitly mention alternatives like execute_command_async for non-blocking execution, but the async transition behavior implies when the async sibling would be relevant. Thus it gives clear context but no explicit exclusions.

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