mermaid_to_workflow

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

Discloses parsing, resolution using /object_info schemas, filling defaults, and returning executable workflow. However, it lacks information on error handling, unsupported Mermaid features, or validation, which is notable without annotations.

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 sentences, front-loaded with primary purpose, no unnecessary words. Each sentence adds essential information about the conversion process.

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?

For a single-parameter tool with no output schema, the description covers input format, processing steps, and output. It could mention supported Mermaid syntax details or limitations, but overall adequate.

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?

The description adds significant meaning beyond the schema's explanation: it specifies Mermaid flowchart text, optional code fences, node labels with class_type names, and connection labels with data types. With 100% schema coverage, this is valuable context.

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 explicitly states the tool converts Mermaid flowchart diagrams to ComfyUI workflow JSON, specifying input format and output. It distinguishes from sibling tools like workflow_to_dsl and visualize_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?

Describes the use case clearly: converting Mermaid text to a ComfyUI workflow. It details parsing steps but doesn't explicitly state when not to use or provide alternatives, though sibling context implies differentiation.

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