drawio_session

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

No annotations provided, so description must carry behavioral info. It lists actions but gives no details on side effects, permissions, error conditions, or specific behaviors (e.g., does save overwrite? Are checkpoints persistent?). The description is too shallow.

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 very short (one sentence), which is concise, but it omits important details. It sacrifices clarity for brevity, so while not verbose, it is under-specified.

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 complexity (multiple actions like checkpoint and undo) and lack of annotations or output schema, the description is insufficient. It does not explain prerequisites, return values, or the exact behavior of each action, leaving the agent with ambiguity.

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 description coverage is 100% as the action parameter explicitly lists all commands. The tool description merely repeats a subset of the schema's parameter description, adding no new meaning beyond what the schema already provides.

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?

Description states it manages a drawio session lifecycle, listing actions like new, open, save, checkpoint, undo, redo. This identifies the domain but lacks a clear verb+resource statement. It distinguishes from sibling tools by focusing on session management rather than drawing or queries.

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 on when to use this tool vs alternatives like drawio, drawio_help, or drawio_query. The agent must infer from the name and description, which is insufficient for effective selection.

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