batch

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

With no annotations, the description carries the full burden. It usefully discloses that results come back per step and that image-producing tools lose their images, but says nothing about ordering/parallelism guarantees, how errors surface when stop_on_error is false, or the exact return shape per step. Adequate but with clear gaps for a meta-execution tool.

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 tight sentences with zero filler; the core capability is front-loaded and the caveat follows immediately. Every clause earns its place.

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?

No output schema exists, yet the description does mention the per-step result granularity, which is the main thing an agent needs. Remaining gaps — error handling under stop_on_error=false and result ordering — are modest for a 2-parameter tool.

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 50%; the operations array format is documented in the schema itself ('command names and params are the same as the tools'). The description adds only a soft example ('all the parts of a chair') and never addresses stop_on_error semantics, so it does not compensate for the uncovered half beyond baseline.

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?

States a specific verb (run) and resource (many tool calls) with a clarifying example ('all the parts of a chair'), and the meta-tool nature makes it unmistakable among the concrete modeling siblings. An agent immediately knows this is the multi-call batching entry point.

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?

Gives an explicit exclusion — 'Not for look/render_image (their images are dropped)' — which is exactly the kind of when-not guidance that prevents wasted calls. It does not, however, state when batching is preferable to sequential calls or what the alternatives are, so it stops short of a 5.

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