nifi_process_group_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds the recursive scope and the backing REST endpoint, which is useful context. It does not add rate-limit, auth, or freshness caveats beyond that, so a middle score is appropriate.

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 parts, front-loaded with the purpose and followed by the endpoint reference. No wasted prose. Not a 5 only because the endpoint line is arguably redundant given the tool name and adds little for an agent.

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?

There is an output schema, so return values need not be explained. Annotations cover safety. The main gap is that the description doesn't clarify how the recursive scoping affects output size or when a non-recursive status is preferable. Otherwise complete for a low-complexity read tool.

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?

One parameter (pg_id) with 0% schema description coverage and a default of 'root'. The description does not explain the id format, the meaning of the default, or whether it accepts a composite path. Baseline 3 for a 1-param tool with an output schema, but the schema gap leaves the description short of adding real meaning.

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/resource combination: throughput and queue statistics for a process group. This is clear and distinguishable from siblings like nifi_flow_status (whole flow) and nifi_queue_listing (queues only). It doesn't explicitly name alternatives, but the scope is precise enough for an agent to select it.

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?

Implied usage only. The 'recursively' modifier and process-group scoping hint at when to use it, but there is no explicit when-to-use vs alternatives guidance, no exclusions, and no mention of siblings like nifi_flow_status or nifi_queue_listing.

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