comfyui_run_workflow

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

With no annotations provided, the description carries the full burden. It only discloses that overrides are non-persistent, but does not mention side effects such as queueing, asynchronous execution, validation behavior, or potential resource consumption. This is a significant gap for a compute-execution tool, so a score of 2.

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 description is a single, front-loaded sentence with no filler. It is concise and to the point, earning a 5.

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?

Despite having an output schema, the description is too sparse for a 5-parameter, no-annotation execution tool. It lacks context on execution flow, parameter purpose, and when to invoke it relative to sibling tools. A score of 2.

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 0%, so the description must explain parameters. It only touches 'overrides' (non-persistent), and does not clarify 'name', 'front', 'validate', or 'client_id'. This leaves most parameters ambiguous, so a 2.

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 uses the specific verb 'Submit' with the resource 'managed workflow to ComfyUI', clearly indicating this tool launches a workflow execution. It also mentions optional overrides, which differentiates it from editing or validation tools among 23 siblings.

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 provides no explicit alternatives or when-not-to-use instructions, though 'managed workflow' implies a prerequisite of an already-saved workflow. The usage is mostly inferred from the tool name and sibling context, so it earns a 3.

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