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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the base is covered. The description adds useful behavioral context by noting results are 'newest first' and describing the return structure, going beyond the annotations without contradicting them.

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 two focused sentences plus a compact return type. Every clause adds value—scope, ordering, contrast, and use cases—with no redundant or vague wording.

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 moderate-complexity read tool, the description includes the return shape and the primary use case. It does not mention error handling or authentication, but the output schema is present and the sibling context clarifies edge cases. Overall, it is adequately complete for an agent to call it 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?

The schema has no per-parameter descriptions (0% coverage), so the description must compensate. It explicitly explains node_id (not a list) and limit ('last N'), but workflow_id is not mentioned or described. Since workflow_id is a required parameter, its role is left to inference, making this partially complete.

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 action (get last N outputs), the resource (a single node across executions), and the scope (node_id, not a list). It explicitly contrasts with get_node_output, making the distinction 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?

It provides explicit usage scenarios: 'Use to compare a node's output over time or find a past run.' It also names the alternative tool (get_node_output) and clarifies when not to use it, giving full guidance.

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