visualize_workflow

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

With no annotations, the description carries the burden. It discloses output format (mermaid syntax) and structure (grouping, labeled connections). It does not explicitly state non-destructive behavior, but the name 'visualize' implies read-only. Minor improvement could be explicit safety mention.

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, no fluff. First sentence states purpose, second adds key details. Efficient and front-loaded.

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 simple conversion tool with fully described schema, the description covers purpose, input, and output format. It lacks comparison to siblings but is otherwise complete for typical use.

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%, so baseline is 3. The description adds context about grouping and labeling, which enriches parameter understanding. The param descriptions are adequate, and the main description provides extra value.

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 states a specific verb ('Convert') and resource ('ComfyUI workflow JSON') and details the output ('Mermaid flowchart diagram', grouping by category, labeled connections). This clearly differentiates it from siblings like 'visualize_workflow_hierarchical'.

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 outlines what the tool does but does not explicitly state when to use it versus alternatives like 'visualize_workflow_hierarchical'. Usage context is implied but not clarified with exclusions or when-not scenarios.

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