Create Editable Architecture Diagram

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

Annotations provide no safety hints (all false), so the description must disclose side effects. It mentions 'self-contained' and 'real SVGs' but omits critical behavior like writing to an output file, handling the 'overwrite' flag, or the distinction between online and local assets. It does not state that this is a non-idempotent file-writing operation.

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 concise sentence with no filler. It packs several useful features, but the adjective-heavy stack ('real SVGs', 'deterministic layout', 'animated colour-coded datapaths') could be streamlined to mention file output explicitly. Still, it earns its place without 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 9-parameter creation tool with no parameter descriptions and no visible output schema in the provided definition, the description is incomplete. It does not cover file creation, overwrite behavior, asset prerequisites, or how this tool relates to the reference diagram tools. The description is too minimal to be fully actionable.

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 0%, and the description explains none of the 9 parameters directly. It hints at theme, layout, animation, and editability, but does not clarify required parameters like 'outputFile', 'nodes', or the 'overwrite' flag. The schema provides structural type/enum information but not semantic guidance.

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 the specific verb 'Generate' with a clear resource ('self-contained native .drawio architecture') and lists distinctive features such as 'deterministic layout' and 'animated colour-coded datapaths'. However, it does not explicitly differentiate from sibling tools like create_reference_drawio, so it misses full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives such as create_reference_drawio, validate_drawio, or prepare_reference_recreation. There is no 'when to use' or 'use this rather than' information, leaving the agent to infer usage from the name alone.

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