ue5_build_batch

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

No annotations are provided, so the description carries the full burden. It clearly discloses the key behavior: atomic rollback if any blueprint fails. This is the critical behavioral trait. It doesn't mention other possible behaviors (e.g., persistence, return format), but for a batch operation the atomicity is the dominant concern, and it is 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?

Two sentences with zero waste. The action and atomicity are front-loaded, and the usage guidance follows immediately. No redundant or filler content.

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 tool with a single well-described parameter and no output schema, the description covers purpose, usage, and the key behavioral guarantee (atomicity). It references the sibling tool's spec for parameter details, which is sufficient. Nothing essential is missing for an agent to decide whether to use it.

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%: the parameter 'blueprints' has a description that already explains it as an array of build specs referencing another tool's schema. The description adds no new parameter information beyond that reference, so baseline 3 is appropriate.

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 states a specific verb ('Create') and resource ('multiple Blueprints') with a defining feature ('atomic batch'). It distinguishes itself from the sibling ue5_build_blueprint by emphasizing the batch aspect, making its purpose 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 says 'Prefer ue5_build_blueprint unless multi-asset atomicity is actually needed', giving a clear when-to-use and when-not-to-use directive, and names the alternative tool. This fully routes the agent.

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