Create Mermaid Artifact

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

Annotations already indicate the tool is not read-only and not destructive. The description adds that it validates code before creating, which is a positive behavioral disclosure. However, it does not detail what happens on validation failure, or if the tool modifies any state beyond creating the artifact.

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 a single sentence with no wasted words. It conveys the core purpose efficiently.

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?

Despite having an output schema, the description is too minimalistic for a tool with 3 parameters (including enums and defaults). It does not explain the error handling (what happens if Mermaid code is invalid), nor does it clarify the relationship between parameters and the created artifact. The tool's behavior regarding file creation or overwriting is omitted.

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%, meaning the schema lacks descriptions for all 3 parameters. The description does not explain the role of the parameters (e.g., that 'code' is the Mermaid code, that 'theme' and 'diagramType' are optional with defaults). This forces the agent to infer meaning from parameter names and enums, which is insufficient.

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 validates Mermaid code and creates an interactive local HTML artifact. It uses a specific verb 'validate' and 'create' and identifies the output as an interactive local HTML artifact. Among siblings, no other tool creates Mermaid artifacts, making it distinct.

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 no guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. There is no mention of when not to use it or any context about required setup (e.g., network, permissions).

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