runCommandBatch

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

No annotations are provided, so the description carries full burden. It mentions 'sequentially' (execution order) but omits critical behavioral traits: error handling (e.g., stops on first failure?), permissions required, output format, timeout/rate limits, or side effects. For a tool executing shell commands on a remote host, this lack of disclosure is a significant gap.

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 a single, efficient sentence with zero waste. It's front-loaded with the core action and target, and every word ('executes', 'multiple', 'shell commands', 'sequentially', 'SSH host') contributes essential information without redundancy.

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 the complexity (remote command execution with potential side effects), lack of annotations, and no output schema, the description is incomplete. It doesn't cover error handling, security implications, or return values, leaving the agent with insufficient context for safe and effective use.

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 description coverage is 100%, so the schema already documents both parameters ('hostAlias' and 'commands'). The description adds no additional meaning beyond implying 'commands' are executed in sequence, which is minimal value. Baseline 3 is appropriate as the schema does the heavy lifting.

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 action ('executes multiple shell commands') and target ('on an SSH host'), with 'sequentially' adding operational detail. It distinguishes from siblings like 'runRemoteCommand' (singular vs. batch) and 'checkConnectivity' (diagnostic vs. execution), though not explicitly named. However, it doesn't fully differentiate from all siblings (e.g., 'uploadFile' is also SSH-related but different purpose).

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., SSH connectivity established), compare to 'runRemoteCommand' for single commands, or specify use cases like batch automation. Without such context, an agent might misuse it when a sibling tool is more appropriate.

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