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

The description discloses key runtime behavior, including the returned shape, the optional execution_id field, and the fact that output is null when no output exists. The readOnly annotation is consistent and the description adds useful edge-case information beyond the 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?

The description is compact and well-structured, front-loading the main purpose and then explaining default versus specific-run behavior and the return format. No unnecessary words are 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 includes the return shape and a key edge case, which makes it self-sufficient for typical usage. It does not cover error scenarios, but the provided context is adequate given the output schema and annotations.

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 prose explains node_ids, workflow_id implicitly through context, and execution_id explicitly with default behavior. The schema has no per-parameter descriptions, but the description covers the important semantics and batch usage.

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: 'Get node outputs in a workflow'. It also distinguishes batch behavior and the optional execution_id scoping, making the resource and action unambiguous.

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 explains when to use the default latest-output behavior versus passing an execution_id for a specific past run. It does not explicitly compare against sibling tools like get_node_output_history, but the usage guidance for the primary parameter is clear.

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