processon_render_mermaid

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

With no annotations, the description carries the full behavioral burden. It discloses that rendering is verbatim, that the tool returns a preview image and an editable link, that the LLM fully owns content, and that repeated calls produce successive versions. This is substantial behavioral context beyond a simple action statement.

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 well organized and front-loaded: a crisp purpose sentence, then workflow context, then a clear argument list. Every sentence carries relevant information; none are redundant or filler. Length is justified by the need to explain supported Mermaid types and parameter usage.

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 three-parameter tool with no annotations and zero schema description coverage, this description is complete. It covers what the tool does, when to use it, how it relates to processon_design_diagram, what input to provide, what output to expect, and the iterative workflow. The existing output schema reduces the need to document return values further.

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, and it does. Each parameter is explained with meaningful detail: mermaid_code is the complete source with example starting tokens, title is optional, and diagram_type is an optional shape hint with concrete examples. This fully adds value beyond the bare schema.

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 opening sentence states a specific verb and resource: 'Render a Mermaid definition YOU wrote into an editable ProcessOn diagram.' The description further distinguishes this from siblings by framing it as the 'edit → render' step and emphasizing that the LLM owns the diagram content, in contrast to design-oriented or generation-oriented tools.

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?

It gives clear workflow context: this is the 'edit → render' step, and you should provide the full Mermaid source, either your own or refined from processon_design_diagram. It also says to iterate by editing the Mermaid and calling again. It does not explicitly state when not to use it or name an alternative tool to use instead, but the positioning is clear enough.

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