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

Goes well beyond the annotations, which only declare it is a non-read-only, non-destructive, non-idempotent write. The description discloses that the flow is always created switched OFF, never overwrites an existing flow, and that inbound webhook URLs are re-slugged — non-obvious side effects an agent must know.

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?

Front-loads the core action, then side effects, then the response shape. Every clause is load-bearing — the OFF state, no-overwrite guarantee, re-slugging, and the missing/redacted lists all matter to correct invocation.

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?

No output schema exists, yet the description explains the two response keys (`missing` and `redacted`) and what each implies for follow-up action. Combined with the side-effect disclosures, an agent has everything needed to import and then act on the result.

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 `file` and `name` documented), so the schema carries parameter semantics and baseline is 3. The description adds context that `file` is the export_flow object, but says nothing about the `name` override behavior beyond what the schema already states.

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 ('Create a new flow') and pins the input to a precise source ('the object neuron_export_flow returns'), distinguishing it from neuron_create_flow and neuron_export_flow without opening a schema.

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?

Clearly scopes when to use it: importing a previously exported flow file. It names the producing sibling (neuron_export_flow) but never explicitly excludes the alternative of building a flow from scratch with neuron_create_flow, so it stops just short of full when/when-not guidance.

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