nifi_get_flowfile_content

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: truncation to max_bytes, base64 encoding for binary payloads, the `encoding` field as the signal, and the backing REST endpoint. It stops short of noting edge cases such as missing/expired flowfiles.

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 clauses, front-loaded with what is returned, then the truncation rule, then the encoding caveat and provenance URL. No filler or repetition.

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 in prose; the description nonetheless usefully discloses that binary payloads come back base64-encoded. With only partial parameter explanation and no alternative routing, it is complete but not exhaustive.

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%, so the description carries the burden, yet it only explains max_bytes (truncation limit). connection_id and flowfile_uuid are named but never explained — that a UUID identifies a specific queued flowfile within a connection is left implicit, only partly recoverable from the URL template.

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: retrieving the content of one queued flowfile. The word 'content' implicitly separates it from the metadata-oriented sibling nifi_get_flowfile, but the description never explicitly names or contrasts that sibling, so sibling differentiation is left to inference.

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?

There is no explicit when-to-use guidance, no stated preconditions (the flowfile must be queued in a connection), and no mention of the sibling nifi_get_flowfile as the metadata-only alternative. Usage context is only implied by the noun phrase 'Content of one queued flowfile'.

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