nifi_list_queue

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the empty-delete-blocked precondition, which is useful context, but does not say whether the operation is sampling/paginated or how FlowFiles are selected.

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 sentences, zero filler, with the scoping precondition placed second. It is efficient and front-loaded, though the terseness is close to under-specification.

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 explained. Still, the description leaves the one required parameter undocumented and does not clarify the ambiguous 'sample' operation, leaving gaps for a read tool with an open-world hint.

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 single required parameter connection_id is never mentioned in the description. With the schema and the description both silent, an agent gets no format or sourcing guidance for the one input it must provide.

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 (sample/list) and resource (FlowFiles on a connection queue), which separates it from the destructive sibling nifi_empty_queue. However, 'sample' is slightly ambiguous versus the annotation title 'List connection queue', so the verb is not as crisp as it could be.

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 description supplies a real precondition ('Connection must not be empty-delete-blocked'), which tells the agent when the call is valid. It never names alternatives (e.g. nifi_empty_queue) or states when not to use this tool, so usage is implied rather than explicit.

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