mermaid_to_workflow

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

With no annotations, the description provides good behavioral context: it uses ComfyUI's /object_info schemas, fills missing inputs with defaults, and returns an executable workflow. However, it doesn't mention error handling or potential limitations for complex Mermaid syntax.

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 two sentences, front-loaded with the core purpose, and every sentence adds meaningful detail. No wasted words, and it efficiently conveys the tool's functionality.

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 parameter, no output schema), the description is mostly complete, covering input format, processing steps, and output. It lacks mention of edge cases like invalid Mermaid or unsupported syntax, but overall sufficiently contextual.

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 single parameter 'mermaid' has full schema coverage. The description adds value beyond the schema by detailing what is parsed (nodes, connections, widget values) and specifying requirements like data type labels, enriching the semantic understanding.

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 converts a Mermaid flowchart into a ComfyUI workflow JSON, specifying it parses node definitions, connections with data type labels, and widget values. It distinguishes itself from siblings like 'dsl_to_workflow' by focusing on Mermaid syntax.

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 usage for Mermaid conversion but lacks explicit guidance on when to use versus alternatives (e.g., 'dsl_to_workflow') or exclusions. No context is given about input validation or when not to use.

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