Render diagram to PNG

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

Annotations are all false and convey little, so the description carries the burden. It adds meaningful behavior: local/offline rendering, returning a file path, and reporting parse errors with offending line numbers. It does not detail overwrite/persistence behavior, but that is covered by the overwrite parameter schema.

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 dense, front-loaded sentences: the first names the action and result, the second gives execution environment and error behavior. There is no filler or redundant restatement.

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?

Even without an output schema, the description explains the return value ('return the path') and error case ('error listing the offending line numbers'). Combined with full parameter schema coverage, the agent has enough information to invoke the tool correctly and interpret results.

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 description does not need to compensate for undocumented parameters. It adds only general context like 'diagram-as-code text,' which maps to the code parameter but does not go beyond what the schema already provides.

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 and resource: 'Render diagram-as-code text to a PNG file and return the path.' It clearly distinguishes itself from the sibling tools: validate_diagram checks code, preview_diagram probably shows a preview, and diagram_syntax is a language reference.

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 implies the use case — produce a PNG file on disk — and adds environment context ('Runs locally with no browser and no network'). However, it does not explicitly say when to prefer render_diagram over validate_diagram or preview_diagram, nor does it mention any exclusion criteria.

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