nifi_replace_flow

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so 'Destructive' largely restates structured data. The added 'Prefer a sandbox PG' recommendation is genuine value beyond annotations, but it still omits what exactly gets destroyed (existing PG contents) and whether the operation is reversible.

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?

Three terse, front-loaded sentences with no filler. The action is stated first, risk second, mitigation third – every sentence earns its place.

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 values need not be described, and annotations cover the safety profile. Still, for a destructive overwrite of a process group, the description does not explain what existing content is replaced or how it relates to the sibling import/apply tools.

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 two inner fields (process_group_id, snapshot) carry no descriptions. The description only echoes 'flow snapshot' from the schema; it adds no format, structure, or sourcing detail for the snapshot payload, leaving the parameter under-explained.

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: 'Overwrite an existing process group with a flow snapshot.' Clear what it does, but it does not differentiate itself from close siblings like nifi_apply_flow_spec or nifi_import_flow, which an agent would need to choose between.

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?

'Prefer a sandbox PG' gives a safety-oriented usage hint, which is useful context. However, it never states when to pick this tool over nifi_import_flow or nifi_apply_flow_spec, so the alternative-selection guidance is only implied.

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