open_drawio_engineering

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

Describes automatic loading of 240+ stencil libraries and includes a syntax warning. However, lacks details on side effects, authentication needs, or output behavior. With no annotations, more disclosure would improve transparency.

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?

Two sentences plus a note, all essential. Front-loaded with main action, no redundant information.

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?

Covers purpose, usage guidance, and a critical syntax constraint. With no output schema, the description is adequate for an editor-opening tool. Could mention synchronous behavior or return value, but not essential.

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% with parameter descriptions. Description adds context that stencils are loaded automatically in the sidebar and lists library categories, providing meaning beyond the schema enum values.

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?

Clearly states it opens draw.io editor with engineering XML and loads stencil libraries. Distinguishes from sibling tool open_drawio_xml by specifying use for engineering block 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?

Explicitly says to use this instead of open_drawio_xml for engineering block diagrams. Provides an important syntax note about avoiding double hyphens in XML comments.

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