flow-add-echo

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

No annotations provided, so description carries full burden. Discloses that it records a step, prints a message, returns an object, and fails if no recording. Could mention that it modifies the flow file, but overall adequate.

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?

Three sentences: purpose, usage, return/fail. Front-loaded with purpose. No filler words, efficient and clear.

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?

Low complexity tool with one parameter. Description includes return value shape and failure condition. No output schema, but return format is mentioned. Complete enough for correct usage.

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?

Only one parameter with schema description covering it fully. Description doesn't add much beyond schema, but the parameter is simple. Baseline 3, but schema coverage is 100%, so 4 is appropriate for clarity.

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?

Clearly states the tool records an echo step in the active flow, explains its purpose (prints a message on replay, acts as a label between tool calls), and distinguishes it from the sibling 'flow-add-step'.

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?

Explicitly says to use when annotating with a human-readable label or checkpoint message, and notes failure condition (no active recording). Provides clear when-to-use and failure context.

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