nifi_list_bulletins

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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds the upstream REST endpoint and the diagnostic intent, but says nothing about ordering, freshness, or filtering behavior. Adds modest value on top of annotations.

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 tight lines: a definition, a backing endpoint, and a usage cue. Front-loaded with the core definition. The endpoint line is arguably low-value to an agent but harmless and brief.

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-value explanation is not required. The main gap is the undocumented limit parameter, but for a simple read-only listing tool the description is otherwise complete enough to call correctly.

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 (limit) with 0% schema description coverage and no mention in the description. An agent cannot tell what limit caps, its units, or its default behavior from either source. The description should compensate for the coverage gap but does not.

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 ('list bulletins') and defines what bulletins are (NiFi's warning and error notices), which is genuinely clarifying for an ambiguous domain term. It doesn't explicitly distinguish from siblings like nifi_flow_status or nifi_system_diagnostics, but the resource is specific enough.

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?

Gives clear diagnostic context: 'The first place to look when a processor is failing but its configuration looks correct.' This is a real when-to-use signal. It doesn't name an alternative or exclusion, but the triggering condition is concrete.

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