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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the output is a Mermaid diagram with a shareable link, it performs four named analyses, and 'nothing is stored' preempts any persistence concern raised by the word 'shareable link'.

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 dense, front-loaded sentences. The core action and output come first, the analytical flags second, and the prerequisite plus non-persistence note close it out with no filler.

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 three-parameter, read-only, idempotent tool, the description covers purpose, output artifact, analytical behavior, prerequisite, and data-retention policy. Even without an output schema, the agent knows what it will receive, which is what an output schema would otherwise have supplied.

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% and the nested flow/system properties are documented in detail (including the method enum semantics), so the schema carries the burden. The description restates the method values (automatic, manual, export/import) but adds no syntax, naming convention, or constraint guidance beyond it — baseline 3.

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?

Names a specific verb (draws) and resource (company's software systems and data flows), plus the concrete output format (Mermaid diagram with a shareable link). The extra clause about what it flags (manual handoffs, duplicate unsynced data, hubs, orphans) further distinguishes it from any sibling tool.

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?

Explicit trigger: 'Use after interviewing the user about their systems,' which tells the agent when in the workflow to call it. No alternatives are named, but the sibling tools (audit_ai_visibility, build_quote, calculate_*) are unrelated in scope, so no exclusion is needed.

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