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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context — that nothing is persisted or published, which readOnlyHint alone does not state — but it omits what happens on invalid Mermaid input.

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?

Two short sentences, front-loaded with the action and output types, with the non-persistence clause appended as a compact caveat. Nothing redundant.

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?

For a simple three-parameter render tool with full annotations and no output schema, the description covers what is produced and that no side effects occur. The remaining gap is error behavior for malformed Mermaid, which matters given the existence of validate_mermaid.

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 partially does by enumerating the three format values (svg, png, pdf) that map to the format parameter. It says nothing about source or the theme parameter's light/dark default, leaving those to the enum and type alone.

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?

States a specific verb (render) and resource (Mermaid source) plus the exact output formats (inline SVG, PNG, PDF). It is naturally distinguishable from the sibling validate_mermaid by verb alone, but never names that sibling or states the render-vs-validate boundary explicitly.

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 phrase "Saves and publishes nothing" sets a useful scope exclusion, but there is no guidance on when to call this instead of validate_mermaid, nor whether validation should precede rendering. Usage is only implied by the purpose statement.

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