create_diagram

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

With no annotations, the description carries the full burden, but it only states that it generates diagrams 'using Graphviz.' It does not disclose whether it writes a file, overwrites existing outputs, requires Graphviz to be installed, what format it produces, or what the return/response looks like.

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 front-loaded sentence with no filler or redundancy, which makes it easy to parse. However, its brevity comes at the cost of missing behavioral and usage context.

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 4-parameter tool with no annotations, no output schema, and a vague 'data' parameter, the description is too thin to be complete. It fails to explain the expected input format, supported output behavior, or how to choose between the enum values, so an agent would need external knowledge to call it correctly.

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%, and the schema already documents the data, type, title, and output parameters, so the description adds no extra parameter-level meaning. The description's mention of Graphviz hints at the data format but does not clarify what 'text description or JSON' should contain.

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 uses a specific verb ('Generate') and names the resource ('diagrams') with concrete examples (flowchart, org chart, mind map), making the tool's core purpose clear. It is distinguishable from siblings like create_chart, though it doesn't explicitly contrast itself with them and omits the 'mermaid' type allowed by the schema.

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?

No guidance is provided on when to choose this tool over sibling tools such as create_chart, nor any conditions, prerequisites, or exclusions. The only implied usage is that it is for diagrams, which is already obvious from the name and description.

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