nifi_flow_status

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered. The description usefully adds that it aggregates two endpoints (/flow/status and /flow/bulletin-board), but discloses no behavioral caveats such as cost, caching, or aggregation scope tradeoffs.

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 compact sentences: the payload summary is front-loaded, followed by a backend endpoint note and a one-line use-case tag. Every clause carries information with no filler, though the endpoint detail is slightly lower value.

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, return values need not be explained, and zero parameters remove all invocation ambiguity. The description is complete enough for the agent to select and call it, though a named alternative would fully close the loop.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to disambiguate, and none of the schema's empty surface needs compensating.

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 ('Aggregate controller status') and enumerates the content returned (running/stopped/invalid counts, queued data, bulletins). The controller-wide scope implicitly distinguishes it from the process-group-scoped sibling nifi_process_group_status, though no sibling is named.

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 fastest way to answer "is anything wrong right now?"' frames the use case as a quick health check, which is implied guidance. However, it names no alternatives (e.g., nifi_system_diagnostics or nifi_list_bulletins) and states no when-not condition, leaving the routing to inference.

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