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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the result is Mermaid source code rather than a rendered image or file, which is genuinely useful. It does not explain whether anything is written or persisted, which matters given readOnlyHint=false.

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 pipe-delimited layout front-loads the trigger and return value, and every segment carries information (trigger, aliases, output type). The repeated title/alias text at the start duplicates the title field and is the only expendable element.

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?

With no output schema, the description correctly states that Mermaid code is returned, and the two-parameter schema is fully documented. Gaps remain around default behavior for 'diagram_type' and what the agent should expect if the prompt is ambiguous, which a generator tool of this simplicity should still cover.

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 100%, so both 'prompt' and 'diagram_type' are already documented with their allowed values. The description adds no further meaning, such as what happens if 'diagram_type' is omitted or how detailed the prompt should be, so the baseline of 3 applies.

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 names a specific output artifact: flow charts, sequence diagrams, or mind maps rendered as Mermaid code, which goes beyond a simple restatement of the name. It does not, however, distinguish itself from diagram-adjacent siblings such as consort_flowchart, leaving the agent to infer which tool to choose when a flowchart is requested.

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 explicit 'USE WHEN' clause states the trigger condition: the user wants a diagram expressed as Mermaid code. The alias list (流程图, 时序图, 思维导图, 画流程) further widens matching for non-English phrasing. It stops short of naming when not to use it or pointing to an alternative tool.

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