get_flow_nodes

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

No annotations are provided, so the description carries the full burden. The phrase 'List all nodes' implies a read-only operation, but the description does not disclose any potential side effects, pagination behavior, return structure, or limitations (e.g., whether all nodes are returned at once or how many). This is minimal coverage for a tool with no annotation safety net.

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?

The description is a single concise sentence that fully conveys the tool's core purpose without redundant words or filler. Every word contributes to the meaning.

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?

Given the tool's simplicity (two parameters, one required), the description is adequate but minimal. It does not explain the return format or any pagination/filtering behaviors, but these may be less critical for a straightforward list operation. However, since there is no output schema, some elaboration on expected results would improve completeness.

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 input schema includes descriptive text for both parameters (flowId, nodeType), providing 100% coverage of parameter meanings. The description adds no additional semantic value beyond what the schema already states, so it meets the baseline of 3.

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 description uses a specific verb 'List' and identifies the resource as 'nodes in a specific flow', making the tool's function immediately clear. It is distinctly different from sibling tools like search_flows or list_flow_groups, which target different entities or operations.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. There is no indication of whether this tool is preferred over search_flows for retrieving flow nodes or if there are any caveats.

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