import_mermaid_flowchart

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

With no annotations available, the description carries the behavioral burden. It discloses that parsing produces a hand-drawn Excalidraw diagram via Sugiyama layout, that output_path is optional, and that an absolute path is returned. It does not mention file overwrite behavior, failure modes for invalid Mermaid, or theme effects, leaving some behavioral ambiguity.

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 compact, front-loaded with the core purpose, and uses a clear Args/Returns structure. Every sentence adds useful information without redundancy.

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 lack of annotations, the description covers the main conversion behavior, input, optional output path, and return value. But it omits the theme parameter, gives no sibling-usage context, and does not clarify what happens when output_path is omitted, so an agent still has notable open questions.

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 description coverage is 0%, so the description must compensate. It explains 'mermaid' as flowchart text and 'output_path' as an optional output file path, which adds some meaning beyond bare schema names. However, the 'theme' parameter is entirely absent from the description, leaving a real gap for an agent deciding whether or how to set it.

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 operation: import Mermaid flowchart syntax and convert it to Excalidraw, including the layout algorithm. It is specific and uses strong verb+resource language, but it does not explicitly differentiate itself from the sibling tool 'import_mermaid'.

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: use this when a Mermaid flowchart needs to become an Excalidraw diagram. However, it provides no explicit guidance about when to prefer this tool over alternatives like import_mermaid or create_flowchart, and no exclusion criteria.

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