batch_commands

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

Annotations indicate destructiveHint=true, and the description adds critical context: atomic-ish behavior, stopping at first error, and that completed steps are a single undo away. This provides valuable behavioral insight beyond the annotation.

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?

Four sentences, front-loaded with key benefit, no fluff. Each sentence serves a purpose: benefit, format explanation, example, recommendation. Excellent structure.

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 essential aspects: purpose, error handling, undo, format, and example. The output schema exists but its details are not needed here. Sufficient for a batch execution tool with one complex parameter.

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 has one parameter with no description. The description fully compensates by detailing the commands array format, object structure with 'type' and 'params', and naming conventions (MCP tool names with auto-translation). Includes 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?

The description clearly states the tool batches multiple commands into one round-trip and undo step, distinguishing it from individual command tools. The verb 'run' and resource 'commands' are specific and unambiguous.

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 recommends use for multi-step edits to reduce round-trips and enable single undo. The error-stop behavior is explained. Lacks explicit when-not-to-use scenarios, but the guidance is clear enough.

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