generate_architecture_diagram

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

Annotations already declare destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds value by defining the return contract ('file paths and an inline PNG preview') and noting that SVG output is self-contained. It omits where files are written and whether output persists, which is a real gap for a tool that writes to disk.

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?

Six tight lines, each covering one spec field, with the verb front-loaded and no qualifying boilerplate. Nothing needs to be cut.

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?

The description states the return values, which matters because no output schema exists, and it explains the structure of the nested spec. The only omissions are the presentation-level options (theme, direction, curve_style, filename), which have defaults and schema-level enums.

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?

Top-level schema coverage is 0%, so the description must compensate, and it does so for the four principal fields: it explains that clusters represent boundaries (accounts, regions, VNets/subnets, AZs, namespaces), that edges are node-to-node, and that nodes map to icon ids. However, it never mentions theme, direction, curve_style, filename, or title, so the documentation covers only part of the spec.

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 first line gives a specific verb and resource: 'Render an architecture diagram with official provider icons.' It also routes to search_icons for icon ids. It does not distinguish itself from diagram_from_terraform or diagram_from_inventory, which also produce diagrams, so it falls short of a 5.

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?

Usage is implied rather than stated: 'type = icon id from search_icons' signals a two-step flow, but the description never says when to use this tool instead of diagram_from_terraform or validate_diagram, or whether validating first is recommended.

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