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

Annotations already cover read-only/idempotent/non-destructive/closed-world, and the description adds genuinely new operational context: a required bearer trial token obtained from POST /agents/trial, a 20 calls/client/day quota, 64 KiB payload and 200-node caps. It also previews what comes back (evidence, classifications, repair suggestions, limitations), which no structured field supplies.

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?

Four tight sentences with zero filler: capability first, exclusions second, returns third... actually returns are folded in early, then auth/limits last. Every sentence carries distinct information an agent needs.

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?

With no output schema, the description still names the return shape, and it discloses the auth prerequisite, quota, and payload ceilings that would otherwise cause silent failures. For a single-parameter, no-sibling tool, nothing required to call it correctly 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% and the single parameter's description already defines a 'sanitized n8n export containing nodes array and connections object.' The description's phrase 'sanitized n8n workflow export' restates that without adding format, sanitization rules, or what makes an export acceptable.

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 and resource ('Free static structural validation of a sanitized n8n workflow export') and enumerates exactly what it detects: missing node references, duplicate IDs, malformed connections, configuration risks. The word 'static' plus the explicit 'does not execute code' line sharply bounds the purpose.

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 negative-scope sentence (no code execution, no credential testing, no URL fetching, no runtime proof) tells an agent precisely which workflow questions this tool cannot answer, which is the main misuse risk. It lacks a positive 'call this when...' framing and there are no siblings to route to, so it stops just short of a 5.

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