mermaid_to_excalidraw

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

No annotations are provided, so the description carries full burden. It discloses that component types are auto-detected from node labels (e.g., 'PostgreSQL DB' gets database styling), which is a key behavioral trait. It also lists supported directions, node shapes, edge types, and subgraphs, providing good transparency 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?

The description is reasonably concise with three paragraphs. The main purpose is stated in the first sentence. Each section adds value, though the list of supported syntax could be slightly trimmed. Overall, it is well-structured 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?

Given the tool's complexity (converting Mermaid flowcharts to Excalidraw), the description covers the supported syntax, auto-detection behavior, and output path. An output schema exists, so return values need not be detailed. Minor omissions like error handling or file overwrite behavior do not significantly detract from completeness.

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 input schema already has 100% coverage and clear descriptions for all three parameters. The description adds value by explaining the supported Mermaid syntax subset and auto-detection, but this is not directly tied to individual parameter semantics. Thus a baseline score of 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?

The description clearly states the tool converts Mermaid flowchart syntax to an Excalidraw diagram, specifying the verb 'Convert' and the resources 'Mermaid flowchart syntax' and 'Excalidraw diagram'. This distinguishes it from sibling tools that create, export, get info, or modify diagrams.

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 details the supported Mermaid subset but does not explicitly state when to use this tool versus alternatives like create_diagram or modify_diagram. It implies usage for conversion tasks but lacks explicit guidance on when not to use it.

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