create_diagram

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

The description discloses that the file becomes immediately visible, which is a useful behavioral detail. But it omits critical behaviors such as what happens if the file already exists (overwrite vs. error) and whether the operation is undoable. With no annotations, this ambiguity creates a safety gap for an 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 and front-loaded, using two sentences to state the action and a key behavioral outcome. Every word earns its place, with no redundancy.

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 create operation with two well-documented parameters, the description covers the core purpose and a key side-effect. However, it lacks information about error handling and existing-file behavior, making it slightly incomplete, especially without annotations to fill the gaps.

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?

Both parameters (filePath and pageName) are fully described in the input schema with clear documentation, so schema coverage is 100%. The tool description itself adds no additional parameter meaning, which is acceptable given the baseline of 3 for high schema coverage.

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 action ('Create') and the resource ('new empty draw.io diagram file'), which distinguishes it from sibling tools like add_node or add_page. The additional note about immediate visibility in VS Code reinforces its unique role.

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 context: use this when you need to create a new diagram file for the VS Code extension. However, it does not explicitly mention exclusions or alternative tools, so it's clear but not exhaustive.

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