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

Goes beyond the annotations (readOnly/idempotent/non-destructive) by disclosing a non-obvious trait: credentials (auth headers, tokens, secret variable values) are blanked and surfaced in a `redacted` list. This tells the agent the export is sanitized and not a full fidelity copy, which materially affects downstream use.

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 tight sentences: the first defines the action and output, the second defines the redaction behavior and the downstream consumer. No filler, and the key information is front-loaded.

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 single-parameter, no-output-schema tool, the description covers purpose, output format, sanitization behavior, and the intended next step. Nothing an agent needs in order to call and use 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?

Only one parameter (id) with 100% schema description coverage, so the schema already documents the UUID. The description implies the flow is identified by id but adds no format or constraint detail beyond the schema, matching the 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?

States a specific verb (Export) and resource (a flow) plus the output format (JSON with format "neuron.flow"). This distinguishes it from read-only siblings like neuron_get_flow and list tools, and the mention of neuron_import_flow pins down the export/import pair.

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?

Explains the intended workflow: pass the returned object to neuron_import_flow to copy the flow into this or another account. That gives clear context for when this tool is the right choice, though it does not explicitly contrast with neuron_get_flow or other retrieval tools.

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