nifi_get_process_group_contents

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds genuinely useful behavioral context beyond that: the non-recursive scoping and the backing endpoint. It does not discuss return size or response shape, but the output schema exists, so the gap is minor.

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 tight sentences, front-loaded with the return contents before the differentiating note. Every sentence carries information; no filler.

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?

With an output schema present and annotations covering the safety profile, the description only needs to convey purpose and scoping, which it does. The one real gap is the undocumented 'verbose' flag, which the description should have clarified given 0% schema coverage.

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 description never mentions the two parameters. The 'pg_id' argument (default 'root') and especially the 'verbose' flag are left entirely unexplained, and the text does not compensate for the coverage gap despite the low baseline requiring it.

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?

Names a specific verb and resource ('direct contents of one process group') and enumerates what it returns (children, processors, connections, ports). It explicitly contrasts with the sibling nifi_flow_tree, so an agent can distinguish the two without opening either 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?

States the selecting condition ('cheaper choice when inspecting a single group') and names the alternative it is not ('Unlike nifi_flow_tree this does not recurse'). This is explicit when-to-use and which-alternative guidance.

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