batch_commands

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

Beyond the destructiveHint annotation, description adds atomic-like behavior details: stops at first error, completed steps are a single undo away. Also mentions auto-translation of command names. Does not cover full error response format.

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?

Well-structured and front-loaded with key idea. Slightly redundant with examples but overall efficient. Every sentence adds value.

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 main points: purpose, usage, limitations (non-batchable tools), format. With output schema present, return value explanation is not needed. Could mention batch size limits or more error details.

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?

Despite 0% schema description coverage, the description fully defines the commands structure with examples: array of objects with 'type' and 'params', and notes auto-translation of names. Compensates completely for schema gap.

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 runs several commands in one round-trip and undo step. It uses specific verbs 'run' and 'batch', and distinguishes from sibling tools by being a batch operation vs individual 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?

Explicitly says when to use (prefer for multi-step edits) and when not to use (composite tools are not batchable). Provides alternatives by listing non-batchable tools by name.

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