Create Mermaid Diagram

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

Description accurately reflects readOnlyHint=false by stating it creates an HTML viewer. Adds context about interactive controls and export. However, it omits details like file output location, error handling, or whether the viewer auto-opens.

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?

Extremely concise single sentence with no filler. Front-loads the primary actions (validate and create). Every word adds value.

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 no output schema, low schema coverage, and annotations lacking details, the description is too brief. Missing information about output format, file handling, error scenarios, and parameter semantics makes it incomplete for a tool that creates a file.

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% and the description provides no information about the three parameters (code, theme, diagramType). Does not explain enums or defaults, leaving the agent without guidance on parameter usage.

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?

Description clearly states it validates Mermaid code and creates an interactive local HTML viewer with zoom and SVG export. Distinct from sibling 'validate_mermaid_syntax' which only validates, and 'detect_mermaid_diagram_type' which only detects type.

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?

Implies usage when both validation and a visual viewer are needed, but does not explicitly contrast with sibling tools like validate_mermaid_syntax. No direct guidance on when to choose this over alternatives.

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