execute_workflow

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

No annotations exist, so the description carries the full burden: it does disclose the asynchronous contract (returns immediately with prompt_id, poll separately) and the environment prerequisite, which is valuable. It says nothing about what happens on invalid workflow, queue-full conditions, or failure modes, which matters for an execution tool with no annotation coverage.

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 return value, then the follow-up tool, then the prerequisite. No filler sentences.

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?

With no output schema, the description usefully states the return value (prompt_id) and how to retrieve results, and it names required environment state. The main gap is failure/error behavior, but for a single-parameter submission tool this covers what an agent needs to invoke it correctly.

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% and the single 'workflow' parameter is documented with its expected origin (from build_workflow or loaded file). The description adds no further detail about the parameter, so the baseline 3 for high schema coverage 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 ('Submit a ComfyUI workflow to run') plus the return value ('Returns prompt_id'), which is more than the bare name conveys. It does not distinguish itself from close siblings like execute_workflow_sync, execute_workflow_stream, or execute_batch, so the agent cannot tell from the description which execution mode to pick.

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 a clear next step ('Use get_execution_status(prompt_id) to check result') and states prerequisites (COMFYUI_HOST set, ComfyUI running). It stops short of saying when to prefer this over the sync/stream/batch execution alternatives listed as siblings.

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