import_mermaid

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the conversion behavior, auto-detection, optional output path, and return of an absolute .excalidraw path. However, it omits details such as what happens when output_path is not provided, whether files are overwritten, how unsupported Mermaid types are handled, and the effect of the theme parameter.

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 concise and well-structured with a one-line summary, an Args section, and a Returns section. It is front-loaded and avoids excessive verbosity, though there is minor redundancy between 'convert to Excalidraw' and 'generates the appropriate Excalidraw diagram.'

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?

The description covers the core purpose, primary parameters, and return value, but it leaves meaningful gaps: the theme parameter is undocumented, the supported diagram types are stated inconsistently with 'any Mermaid diagram', and there is no guidance about alternatives among sibling tools. Given no annotations and 0% schema description coverage, the description is only minimally 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 description coverage is 0%, so the description must compensate. It adds meaningful context for mermaid ('Mermaid diagram text (flowchart or sequenceDiagram)') and output_path ('Optional output file path'), but it completely omits the theme parameter, which appears in the schema with a default. The description improves on the bare schema but is incomplete for all three parameters.

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 a specific verb and resource: 'Import any Mermaid diagram and convert to Excalidraw.' It also mentions auto-detection of flowchart or sequence diagram types, which hints at a distinction from sibling tools like import_mermaid_flowchart. However, the overbroad claim of 'any Mermaid diagram' followed by only two supported types creates slight ambiguity.

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 context: use this tool when you have Mermaid diagram text and want an Excalidraw file. However, it provides no explicit guidance on when to prefer this over siblings like import_mermaid_flowchart, create_flowchart, or create_sequence_diagram, and it does not state any exclusions or alternatives.

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