execute_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 usefully discloses the blocking/polling model and the environment prerequisite, but says nothing about what happens on partial failure beyond the stop_on_error flag, whether per-workflow results or errors are returned, or how timeouts surface.

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?

Three short sentences, front-loaded with the action and followed by the execution model and prerequisite. Little waste; the first sentence mildly repeats the tool name but the polling clause immediately 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?

There is no output schema and no annotations, so the description should explain what a batch call returns and how failures are reported. It covers the invocation model (polling, defaults, host requirement) but leaves the result shape and error-aggregation semantics undefined.

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 100%, so every parameter including defaults is already documented in the schema. The description only echoes concurrency and stop_on_error, adding no format or behavior detail beyond the structured fields, so the baseline 3 applies.

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 and resource ('Execute multiple workflows in batch') and adds scope detail ('submits each workflow and waits for completion (polling)'), which separates it from the single-workflow siblings. It does not, however, distinguish itself from execute_chain, which is the closest-looking sibling.

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 gives the precondition 'Requires COMFYUI_HOST' and mentions optional concurrency and stop_on_error, which implies the batch usage context. It never states when to prefer this over execute_workflow, execute_workflow_sync, or execute_chain, so the agent must infer the choice.

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