open_drawio_mermaid

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

No annotations are present. The description only states the tool's action without disclosing behavioral traits such as destructiveness, authentication requirements, or side effects (e.g., whether it modifies data or just displays). This leaves ambiguity for the agent.

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 concise: two sentences. The first sentence states the core action and content format, the second lists supported diagram types. There is no unnecessary information, and key details are front-loaded.

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's low complexity (3 parameters, no output schema, simple UI action), the description covers essential aspects. It could mention that the tool likely opens an interactive editor (non-destructive), but it is generally complete for agent decision-making.

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 coverage is 100%, so the input schema already describes all parameters. The description adds a list of supported diagram types, which provides context but does not significantly enhance parameter understanding beyond the schema's descriptions.

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 opens the draw.io editor with a diagram generated from Mermaid.js syntax or a URL, and lists supported diagram types. This distinguishes it from sibling tools (open_drawio_csv, open_drawio_xml) which handle different formats.

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 for Mermaid-based diagrams but does not explicitly state when to use this tool versus alternatives. No guidance on when not to use it or prerequisites is provided.

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