analyze_drawio

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

With no annotations, the description carries the full behavioral burden. It clearly discloses that the tool validates and parses, and that it returns both validation issues and parsed structure. However, it does not explain error handling for malformed XML, whether any side effects occur, or how issues are represented.

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 two short clauses: it states what the tool does and what it returns. Both pieces of information earn their place, the core operation is front-loaded, and there is no fluff or 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 single-parameter analysis tool, the description covers the operation and return value sufficiently to make a call. However, with no output schema and no annotations, it leaves the return format vague and does not explain how this tool relates to the sibling validate and parse tools, so an agent may not know when this is the right choice.

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% for the single xml_content parameter, so the schema already documents it. The description adds no substantial meaning beyond restating that the content is Draw.io XML, which matches the schema. The baseline of 3 applies.

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 names a specific resource (Draw.io XML) and states the exact operations: validate syntax and parse structure. It also says the tool returns both validation issues and parsed structure, which distinguishes it from the separate validate_drawio and parse_drawio siblings, though it does not name them explicitly.

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?

There is no guidance about when to use analyze_drawio versus validate_drawio, parse_drawio, or the other sibling tools. The description implies it combines validation and parsing, but it never states that an agent should choose this tool when it needs both results together.

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