ue5_run_batch

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

No annotations are present, so the description must disclose behavior itself. It discloses the default stop-on-first-failure behavior and the whitelist restriction on commands, but does not discuss side effects, return format, or permission implications, which matters for a tool that executes commands.

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 core behavior and usage guidance are packed into three short clauses, with no filler. The bilingual repetition is mild but keeps each version compact.

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?

For a two-parameter batch tool, the description covers selection and default failure behavior, but the absence of an output schema means the agent is still left without information about what the call returns (per-step results, logs, or aggregate status) or whether successful steps are committed. This is a substantive gap for a batch executor.

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 coverage is 100%, so a baseline of 3 applies. The description adds meaning by restricting command values to a whitelist and emphasizing that the steps array represents an ordered multi-step sequence, which is not fully explicit in the schema.

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 opens with a specific verb and resource ('Execute a whitelisted-command batch') and clarifies it is a multi-step task in a single round trip. It also contrasts with single-operation tools, so an agent can distinguish this from the many sibling execution tools.

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?

It explicitly says this tool is for sequences and that for a single operation the dedicated tool should be preferred. It does not name the specific sibling (e.g., ue5_execute_command), but the sequencing-vs-single-operation criterion is clear.

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