open_in_drawio

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

There are no annotations to describe side effects or error behavior. The description is straightforward but does not disclose what happens if the file is missing, whether the app launch is synchronous, or any potential side effects on the file system.

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, concise sentence with no unnecessary words or repetition, providing exactly the essential information about the tool's purpose.

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 simple tool, the description covers the core action, but it lacks details about the output schema, error handling, or any prerequisites. Given the tool's simplicity, this is adequate but not fully comprehensive.

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 has no description for input_path, and the tool description only indirectly implies it is the path to the .drawio file. While the name and context make it likely, the description does not explicitly define the parameter's meaning or expected format.

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 explicitly states the tool's action ('Open a .drawio diagram file') and the target application ('local Draw.io Desktop GUI app'), making it clear and distinct from sibling tools that create, parse, export, or validate diagrams.

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 use this tool versus alternatives. The description does not mention any conditions or preferences, leaving the agent without clear selection criteria.

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