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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds valuable behavioral context: it explains that the tool generates a new workflow ('Returns workflow JSON'), describes the internal structure ('Manual Trigger -> Replay Seed -> target node'), and clarifies how optional parameters affect behavior ('pins what the target sees'). No contradictions with 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 concise with five sentences, each adding essential information: main purpose, workflow structure, optional params, use case, and return value. No redundant or unnecessary words, and it is front-loaded with the primary action.

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 complexity (4 params, 2 required) and presence of output schema, the description covers the main workflow, parameter effects, and output. It does not mention error scenarios or node existence checks, but for a non-destructive, read-only tool this is acceptable. The description is largely complete.

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 coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining that inputItems or execution 'pins what the target sees' and that inputItems become '{ json: ... }' items. This clarifies the parameter usage in the context of building a replay workflow.

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 builds a self-contained replay workflow for a single node, using the verb 'build' and specifying the resource 'replay workflow'. It distinguishes from siblings like execution_list and workflow_create by focusing on isolating one node for debugging, as stated in 'iterating on one stubborn node without re-running the whole pipeline'.

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 clear when-to-use guidance: 'useful for iterating on one stubborn node without re-running the whole pipeline'. However, it does not explicitly state when not to use this tool or name alternative tools from the sibling list, which would strengthen the guidelines.

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