Batch Commands

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

With no annotations, the description must disclose all behavioral traits. It correctly forbids destructive commands, but does not mention execution order, atomicity, error handling, response format, or limits. These omissions reduce transparency.

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, well-structured sentences that immediately convey the core function, format, and restrictions. No unnecessary words.

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?

While the description covers purpose and restrictions, it lacks details on response format, error reporting, execution behavior (sequential vs parallel), and limits on batch size. For a batch tool, these are important 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?

The only parameter 'commands' has an empty schema description. The description explains its structure as an array of objects with 'type' and 'params', adding meaning beyond the schema. However, it does not list valid command types or provide an example.

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 the tool executes multiple commands in a single round-trip, specifies the command format, and explicitly lists destructive commands that are excluded, which distinguishes it from individual sibling commands.

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?

Provides explicit guidance: use batch for non-destructive multiple commands; use individual tools for destructive commands. Clearly tells when to use versus alternatives.

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