nifi_import_flow

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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior. The description adds one genuinely useful behavior beyond them: that placing a card can shift existing cards clear. However, it omits permission requirements, idempotency implications of re-importing the same snapshot, and what the compact vs. verbose return actually contains.

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 short sentences, front-loaded with the core action and followed by the placement rule. No wasted words, though the placement detail could be folded into a tighter clause.

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?

An output schema exists so return formatting needn't be explained, but for a mutation tool with three required parameters and zero schema descriptions, the definition leaves the agent without enough to construct a valid snapshot or parent reference.

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 0% and the nested params object carries six fields (x, y, verbose, snapshot, parent_id, group_name). The description only glosses x/y placement behavior and says nothing about the required parent_id, group_name, or the snapshot payload format, so it fails to compensate for the coverage gap.

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?

The description states a specific verb and resource: importing a versioned flow snapshot as a new child process group. This distinguishes it from sibling tools like nifi_create_process_group and nifi_replace_flow, though it never explicitly names an alternative to differentiate itself.

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 only guidance is about placement ('omit x/y to take the next free cell'), which is a geometry rule, not a when-to-use rule. There is no indication of when to choose this over nifi_replace_flow, nifi_apply_flow_spec, or nifi_create_process_group.

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