render_mermaid

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

Annotations are minimal (only title) with no destructive or readOnly hints. The description adds value by explaining output behaviors (localhost URL, file saving, raw data) and hints at non-destructive rendering. However, it does not disclose potential side effects, authorization needs, or whether the tool modifies existing resources. With no annotations, the description carries the burden but is not fully transparent.

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 with a clear first sentence, followed by a bullet-like list of output options and examples. It front-loads the core purpose. The examples section is slightly lengthy but informative. Overall efficient with minimal redundancy.

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 high complexity (16 parameters, nested objects, no output schema), the description is incomplete. It fails to explain most parameters, does not describe return value structure for each output type, and provides no guidance on sequencing with sibling tools. The examples help but do not compensate for the missing detail on half of the parameters.

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 mentions a few parameters (theme, backgroundColor, format, output) in examples but does not explain over 10 parameters (e.g., quality, darkMode, filePath, sequence, flowchart options). The description says 'comprehensive styling and output options' but lacks detail, leaving many parameters ambiguous.

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 'Render a Mermaid diagram' with specific output formats (SVG, PNG, JPG, PDF) and mentions styling options. The verb 'render' and resource 'Mermaid diagram' are specific and distinct from sibling tool 'render_plotly' which suggests Plotly charts.

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 clear context on output options (link, filepath, raw) and includes examples for common use cases. However, it does not explicitly state when to use this tool versus the sibling 'render_plotly', though the diagram type implies it. No explicit exclusions or alternatives are given.

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