validate_workflow

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

Without annotations, the description carries full weight. It discloses that the tool does not execute (key behavioral trait) and returns errors/warnings, but lacks details on side effects, permissions, or rate limits. It is adequate but not comprehensive.

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 sentences with clear, front-loaded purpose. Every word adds value; no redundancy or fluff. Ideal conciseness for a simple validation tool.

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?

Given the tool's simplicity (one param, no output schema), the description adequately covers purpose and return type (list of errors/warnings). It is complete enough for an agent to understand usage without needing additional context.

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% with one parameter. The description does not add parameter-specific details beyond the schema's 'ComfyUI workflow in API format'. Baseline 3 is appropriate since the schema handles the param definition.

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 the tool's purpose as validating a ComfyUI workflow without execution, listing specific checks (missing node types, broken connections, etc.). This is distinct from siblings like 'analyze_workflow' or 'enqueue_workflow'.

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 implies use before execution but does not explicitly state when to use this tool versus alternatives like 'analyze_workflow'. There is no mention of when not to use or alternatives, leaving the agent without clear guidance.

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