read_drawio

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

No annotations provided, so description carries full burden. It discloses return format (structured JSON), supported formats (uncompressed mxGraphModel XML and .drawio), and implies read-only behavior. Could further emphasize no file modification, but is adequate.

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 concise sentences with front-loaded action verb 'Reads and parses'. No redundancy or filler. Every sentence adds value: purpose, return format, usage guidance, and format support.

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 no output schema, description explains return format well. For a read-only tool with 3 parameters fully covered in schema, description is sufficiently complete. Could mention error behavior or file existence, but not critical.

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%, baseline 3. Description adds meaning beyond schema by clarifying that include_style_details provides parsed style properties and include_geometry includes position/size. Adds context to file_path (absolute path) and boolean meanings.

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 clearly states it reads and parses .drawio/.xml files, returning structured JSON with shapes, edges, and properties. Distinguishes from siblings like create_* or export_drawio by focusing on reading/analysis.

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 states when to use: analyze existing diagrams, extract component lists, or understand structure before modifications. Does not explicitly mention when not to use or name alternatives, but context of sibling tools implies those are for creation or different formats.

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