mermaid_to_excalidraw

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

The description details the supported Mermaid subset and auto-detection of component types. With no annotations, it carries the full burden and mostly covers behavior, though missing details on file overwrite or error handling.

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 succinct and well-structured with bullet points for supported features. Every sentence adds value, and the most important information is 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 moderate complexity and presence of an output schema, the description covers essential aspects like supported syntax and auto-detection. Minor gaps exist (e.g., error handling), but overall it is sufficiently complete.

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%, baseline is 3. The description adds value beyond the schema by elaborating on the supported syntax and theme options (e.g., 'professional' uses Helvetica). This aids parameter 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 Mermaid flowchart syntax into an Excalidraw diagram. It specifies the supported subset, which distinguishes it from sibling tools like create_diagram, get_diagram_info, and modify_diagram that do not involve conversion.

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 provides clear context on when to use the tool—when you have Mermaid syntax and need an Excalidraw diagram. However, it does not explicitly state when not to use it or mention alternatives, though the context is adequate.

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