workflow_to_dsl

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

No annotations provided; description carries full burden. States it's a pure conversion, mentions experimental nature, gives format example. No destructive behavior implied. Adequate for a conversion tool.

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 plus a syntax example, all essential. Front-loaded main action, then round-trip and format info. No wasted words.

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?

No output schema, but description gives format example. Parameter well-documented in schema. Complexities low. 'Experimental' warns about stability. Slightly missing explicit return type, but sufficient.

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?

Only one parameter, schema description covers it fully (ComfyUI workflow format). Tool description does not add extra meaning beyond what schema already provides. Baseline 3 is appropriate.

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?

Clearly states the conversion from ComfyUI API workflow to DSL format. Distinguishes from sibling dsl_to_workflow by mentioning reverse operation. Provides benefits: compact, human-readable, lossless round-trip.

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?

Implies use when editing workflows is needed, as DSL is easier than raw JSON. Mentions alternative dsl_to_workflow for reverse. Gives syntax example. Lacks explicit when-not-to-use, but context is clear.

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