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

Annotations only declare readOnlyHint and openWorldHint; the description adds real substance beyond them — how risk levels are derived ('computed from the node's own resource + operation'), what add_gates returns (a copy with an Approve/Decline step wired in), and explicit non-mutation guarantees. This is exactly the behavioral context annotations cannot carry.

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?

A single dense paragraph, front-loaded with the core action ('Read an existing n8n workflow JSON … say what it would do before it runs') followed by the enumerated outputs. Every clause is informative; only the parenthetical channel list is mildly expendable.

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 read-only inspector with an output schema, complete annotations, and full schema coverage, the description covers everything an agent needs: what it reads, what it returns, the opt-in gating branch, and the no-side-effect guarantee. Nothing material is missing.

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 coverage is 100%, so 3 is the baseline, but the description adds meaning: it explains the interaction model behind ask_via ('one-tap Approve / Decline step (Slack, Telegram, Gmail…)') and clarifies that add_gates yields a separate gated_workflow copy rather than altering the original. Adds modest value over the schema text, which already documents both optional params.

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?

States a specific verb ('read/inspect') and resource ('an existing n8n workflow JSON') and then enumerates exactly what it reports: per-node risk labels, ungated irreversible steps, existing approvals, and unconnected accounts. This clearly separates it from the mutation/creation siblings (make_n8n_workflow, plan_automation, do) without needing to name them.

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?

'before it runs' plus 'Nothing is run; the original is not modified' gives a clear usage context: pre-flight inspection of an existing workflow. It also explains the add_gates branch condition. It stops short of naming the sibling to use instead for authoring or executing, so it is clear context without explicit exclusions.

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