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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one useful behavioral fact beyond that: the returned node can carry very large parameter payloads, which is why the chunked alternative exists. It does not describe error behavior for a missing node or the general shape of what comes back.

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?

Two sentences, each earning its place: the core action first, then the large-payload escape hatch. No redundancy, no restating of the title or schema, and the most important information is front-loaded.

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?

For a simple two-parameter read tool with full schema coverage and complete annotations, the description supplies what is needed to select and call it, plus the large-parameter caveat. The only modest gap is that there is no output schema, so the returned node shape (and the fact that its parameter values may be verbose) is only hinted at rather than described.

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 100% and both parameters (workflowId, nodeId) are documented directly in the schema, so the baseline applies. The description adds no format, scoping, or lookup semantics beyond what the schema states.

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?

Description gives a specific verb and resource ("Get a specific node by ID from a workflow") and names the sibling workflow_get_node_parameter as the alternative for a particular case. The retrieval target and key are unambiguous, though it does not differentiate itself from other workflow_* readers such as workflow_get or workflow_get_edges.

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?

It states an explicit routing condition: when parameter values are very large, use workflow_get_node_parameter instead. That is genuine when-to-use guidance tied to a named alternative. It stops short of saying when this tool is the wrong choice in other situations (e.g. listing many nodes, or needing only structure).

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