nifi_get_processor

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description does add one genuine disclosure beyond the structured data: "secrets redacted", which tells the agent not to expect sensitive property values. It says nothing about behavior for a missing/invalid component id, which is the remaining gap.

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?

It is a single short fragment with no filler, which is structurally efficient, but it is under-specified rather than concise — there is no verb and no complete sentence. It reads as a note rather than a 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?

With an output schema present, return values need not be re-explained, yet the description lists them anyway; the annotations cover the safety profile. For a one-parameter read tool this is close to adequate, but the component_id semantics and error behavior remain unaddressed.

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 reported as 0%, so the description is expected to carry parameter meaning. It does not: the only parameter, component_id, is never explained (format, where to obtain it, error on unknown id), and the verbose flag is left entirely to the schema. A bare 2 reflects that gap.

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?

The fragment names a specific resource (one processor) and enumerates what is returned: state, validation errors, properties. Combined with the tool name, an agent can distinguish it from nifi_list_processor_types (enumerate types) and nifi_get_processor_definition (type schema) without opening either schema. It stops short of a full verb-resource sentence, keeping it out of the 5 tier.

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 when-to-use guidance, no statement of prerequisites, and no routing to alternatives such as nifi_get_processor_definition or nifi_update_processor. The agent must infer usage purely from the name and the returned-field list.

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