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

The description discloses the exact return shape and included fields, which is strong behavioral transparency. The read-only and non-destructive nature is already covered by annotations, and the description adds a meaningful performance note about avoiding whole-workflow loading.

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 concise, front-loaded with the main purpose, and efficiently packs return shape and usage guidance into a few sentences. No redundant or filler content is present.

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?

The description covers return format and the main alternative tool, but it leaves parameter meanings and edge cases undocumented. Given that the schema has zero description coverage, the description partially compensates but is not fully complete for an agent needing to invoke the tool correctly in all situations.

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 provides no descriptions for workflow_id or node_ids, and the description gives only implicit hints such as 'node(s)' and 'whole workflow'. It does not explicitly define what values are expected or how node_ids relate to the workflow, so parameter semantics are minimally addressed.

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 clearly states the tool's purpose: getting a node's setup including config, type, handles, output, disabled, and has_mock without loading the whole workflow. It also distinguishes itself from the sibling get_node_output by noting the leaner alternative for output-only needs.

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 explicitly advises using get_node_output when only a node's output is needed, which provides a clear alternative and condition. It also implies the primary use case is configuration-focused, though it does not enumerate every possible alternative in the large sibling set.

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