batch_execute

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explains error handling (stops on first error unless continueOnError is true), the inverse alias (stopOnError), the nesting restriction, and the undo waypoint behavior. It could mention return-value details, but the core behaviors are well covered.

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 extremely concise—two sentences covering purpose, structure, error behavior, and usage guidance. It is front-loaded with the main purpose and contains 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?

Given the tool's complexity (executing multiple arbitrary sub-tools) and the absence of an output schema, the description should explain what the return payload looks like (e.g., per-command results, error reporting). It does not, and it also does not specify whether partial mutations are rolled back on error. The description covers behavior well but leaves these important details unaddressed.

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 75%, covering commands, waypoint, and stopOnError. The description adds value by clarifying the alias relationship between stopOnError and continueOnError and confirming the command shape. However, continueOnError itself lacks a schema description, and the description does not elaborate further on parameter formatting beyond what the schema already provides.

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's purpose: running several RoBridge tool calls in one request as a single undo waypoint. It uses a specific verb ('Run') and resource ('RoBridge tool calls'), and distinguishes itself from sibling tools like execute_luau by highlighting the batching aspect.

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 explicit usage guidance by recommending this tool 'over many round-trips for related mutations' and explicitly rejecting nested batch_execute. It does not name specific alternative tools, but the context of batching vs. individual calls is clear.

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