nifi_create_process_group

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

Annotations already declare the mutation profile (readOnly=false, destructive=false, idempotent=false, openWorld=true), so the bar is lower, and the description still adds real behavior: omitting x/y picks the next free 424x288 cell, and an overlapping x/y is shifted down with the shift reported in warnings. It does not mention permissions or parameter-context interaction, keeping it from a 5.

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 short lines, front-loaded with the core action and the placement rule. Every sentence carries information an agent would otherwise have to guess.

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 the description still flags the warnings field for the overlap case. For a mutation tool with full annotation coverage and a parameter-context option documented in the schema, this is nearly complete.

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?

With the schema carrying no description for x/y, the description compensates by defining their default placement behavior and the overlap-shift rule. It says nothing about name, parent_id, comments, or verbose, so the less tricky parameters are left to the schema.

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 an empty process group') and immediately clarifies scope by telling the agent to build flows inside one of these rather than on root. That scope statement distinguishes it from sibling mutators like nifi_create_processor or nifi_create_connection 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?

'Build every new flow inside one of these, not on root' gives explicit when-to-use guidance with a clear negative case. It stops short of naming an alternative tool for the root case, so it is clear context rather than full routing.

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