convert_mermaid_to_jpeg

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the conversion outcome and says nothing about default output naming, overwrite behavior, optional parameters, external dependencies, or failure modes.

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 a single short sentence that front-loads the core action and output format. There is no filler and no repetition of schema details.

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 straightforward conversion tool, the core operation is clear, and the schema covers parameters. However, with no output schema or annotations, the description leaves unspecified how the optional output_file behaves when omitted, which is relevant for correct invocation.

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 all six parameters are already documented with defaults and purpose. The tool description adds no parameter-level detail, but the schema adequately carries that burden, making the baseline score appropriate.

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 states a specific conversion action, identifies the input resource as a mermaid diagram file, and specifies the output format as JPEG. The mention of 'mermaid' clearly distinguishes it from the sibling convert_md_to_jpeg, even though the sibling is not explicitly named.

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 intended use is implied by the description and tool name: use this tool when you have a Mermaid diagram file to convert to JPEG. However, there is no explicit guidance about when not to use it or when to choose the sibling convert_md_to_jpeg tool instead.

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