Generate All Diagrams

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

Discloses that it 'writes the full set to DIAGRAMS.md' and groups by source artifact. Annotations already indicate idempotency and non-destructiveness, and description adds meaningful output context beyond annotations.

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. Main action in first sentence, output detail in second. No filler, front-loaded, easy to parse.

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 simple tool with 2 params, no output schema, and safe annotations, description is complete. It explains output file and diagram types. Minor gaps: doesn't explicitly state dependency on existing artifacts or batch behavior.

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% (both params documented). Description does not add additional parameter-level meaning, but baseline 3 is appropriate as schema provides sufficient detail.

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?

Clearly states it generates ALL diagram types for a feature, listing specific types (architecture, sequence, ERD, flow, dependency, traceability). Distinguishes from sibling tools like sdd_generate_diagram by emphasizing the 'all' aspect.

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?

Provides clear context ('Generates ALL diagram types for a feature in one call') implying use when complete set is needed. However, does not explicitly state when not to use, nor mention alternatives like sdd_generate_diagram for single diagrams.

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