render_graphviz

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

Discloses syntax requirements (digraph G, -> vs --) and engine options with their typical uses. With no annotations, it carries the burden well, though tips on error handling or limits are missing.

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?

Very concise: single paragraph with logical flow from purpose to use cases to important notes to engine guide to additional resources. No wasted words.

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 no output schema and moderate complexity (3 params), description covers syntax, engines, and use cases adequately. Minor omission: difference between SVG and PNG output.

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 covers all parameters (100%), but description adds extra context: engine guide (e.g., 'sfdp=large graphs') and syntax rules. Adds value beyond 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?

States exactly what it does: 'Render a Graphviz DOT diagram to SVG or PNG.' Differentiates from siblings like render_mermaid and render_d2 by specifying Graphviz 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?

Provides clear use cases: dependency graphs, network diagrams, tree structures, large auto-layout graphs. Also mentions calling get_tool_guide for examples, but does not explicitly exclude scenarios.

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