validate_drawio

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

No annotations are present, so the description carries the full behavioral disclosure burden. It clearly states that validation covers syntax and structure and that the result includes errors, warnings, and suggestions, giving the agent a solid contract. It does not explicitly state that there are no side effects, but validation is inherently non-mutating.

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 a single sentence with no waste. It front-loads the verb and resource, then states the return value components. Every word contributes to the agent's understanding.

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 validation tool with no output schema, the description covers the essential input/output contract: what is validated and what result categories to expect. It lacks explicit response format details and sibling-tool comparison, but these are minor for the tool's simplicity.

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%, so the parameter already carries full meaning ('The Draw.io XML content to validate'). The tool description adds no extra parameter-level detail such as size limits, encoding expectations, or formatting requirements, so baseline 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 uses a specific verb ('Validate') and a clear resource ('Draw.io XML syntax and structure'), and it states what the result contains (errors, warnings, suggestions). This clearly differentiates it from siblings like parse_drawio and analyze_drawio without needing to open the schema.

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 purpose strongly implies when to use it — when Draw.io XML needs syntax/structure validation — but there is no explicit guidance about when not to use it or which sibling tool to prefer for parsing or analysis. The context is clear, but no alternative routing is provided.

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