generate_mermaid_svg

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the tool 'always saving the result as an SVG file', which is a useful behavioral trait, but lacks details on error handling, performance, or side effects like file overwriting. It partially compensates for missing annotations but leaves gaps.

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 appropriately sized and front-loaded, with the core purpose stated first. It uses two sentences efficiently, though the second sentence could be slightly more concise by combining ideas. Overall, it avoids unnecessary details and is well-structured.

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 the complexity (a file-saving tool with 4 parameters), no annotations, and no output schema, the description is moderately complete. It covers the main action and output format but lacks details on error cases, file naming conventions beyond the 'filename' parameter, or what happens if the file already exists. It's adequate but has clear gaps for a tool that modifies the filesystem.

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 the schema fully documents all parameters. The description adds minimal value beyond the schema by mentioning 'customizable themes and background colors', which aligns with the 'theme' and 'backgroundColor' parameters but doesn't provide additional semantics. Baseline 3 is appropriate as the schema does the heavy lifting.

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's purpose with specific verbs ('Generate SVG content', 'save it to a file') and resources ('from Mermaid diagram syntax'), and distinguishes it by mentioning the output format (SVG) and customization options (themes, background colors). It explicitly states the action and result format.

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, prerequisites, or exclusions. It mentions the tool's functionality but lacks context for decision-making, such as when to choose this over other rendering methods or file formats.

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