Create a .drawio XML diagram file with nodes and edges at specified coordinates, enabling programmatic diagram generation for Draw.io.
Create a new .drawio XML diagram file with nodes and edges at specified coordinates.
| Name | Required | Description | Default |
|---|---|---|---|
| edges | Yes | ||
| nodes | Yes | ||
| page_name | No | Page-1 | |
| output_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description mentions file creation but does not disclose whether it overwrites existing files, what return value is provided, or error handling behavior. No annotations are present to supplement this information.
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, direct sentence that efficiently conveys the core functionality without unnecessary words or repetition. It is well-structured and easy to parse.
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 the tool has four parameters including nested arrays and a default value, the description and schema lack essential details such as node/edge format, coordinate semantics, page_name usage, and output behavior. The absence of annotations compounds the incompleteness, making the tool difficult to use correctly without external knowledge.
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?
The schema lists parameters with titles only, and no descriptions are provided. The description mentions 'nodes and edges at specified coordinates' but does not explain the structure or how coordinates are specified, leaving the agent without sufficient parameter detail.
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 clearly states the tool creates a new .drawio XML diagram file with nodes and edges at specified coordinates. The verb 'Create' and the format specification make the purpose unambiguous, and it distinguishes from sibling tools that generate specific diagram types.
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 usage when a new generic diagram is needed, but it does not explicitly state when to prefer this tool over siblings like generate_er_diagram or generate_sequence_diagram. There is no guidance on prerequisites or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.