comfy_cli_workflow

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

Discloses that validation checks without submission (non-destructive) and run submits asynchronously by default with wait option for synchronous outputs. No annotations exist, so description carries full burden adequately.

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 concise, front-loaded sentences with no redundant information. Every word adds value.

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?

Lacks crucial details such as prerequisites (comfy-cli installation), return values, error handling, and behavior differences between local/cloud. Given no output schema and many sibling tools, description is incomplete.

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 only 17% (workspace only), yet description only adds context for 'wait' (set wait=true to await outputs). Other parameters like where, timeoutSeconds, and workflowPath remain unexplained.

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 clearly states it validates or runs workflow files using comfy-cli, distinguishing between the two actions. However, it does not differentiate from sibling tools like validate_workflow or run_workflow_url.

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?

Provides basic context for using validate vs run and async vs wait, but no guidance on when to prefer this tool over numerous siblings such as validate_workflow, enqueue_workflow, or run_workflow_url.

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