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

With no annotations provided, the description carries full burden. It discloses meaningful behavioral traits: the component stays linked (updates propagate to all tests), the reference expands at replay time, and a user-ownership constraint exists ('both must belong to the authenticated user'). This is solid behavioral disclosure for a mutation operation, though it doesn't address reversibility or failure behaviors.

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 a single tight paragraph covering purpose, linking behavior, replay expansion, param bindings, and ownership constraint. It's front-loaded with the core purpose. Slightly dense but every sentence earns its place; no filler.

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 tool is moderately complex (4 params, nested object paramBindings, ownership constraints, live-reference semantics), and the description covers the live-linkage behavior, replay expansion, param substitution, and auth requirement. No output schema exists, so the description could note what the operation returns, but the behavior is otherwise well documented.

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%, so each parameter is already documented in the schema. The description adds the paramBindings semantics ({{name}} placeholders) which complements but slightly overlaps the schema. Since all 4 params are fully documented in-schema and the description reinforces their meaning, baseline 3 is appropriate.

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 inserts a LIVE reference to a reusable component into a saved test after a given step, differentiating it from copying/detaching behaviors. It clarifies the linked-not-copied semantics and expansion at replay, distinguishing it from sibling tools like flow_recording_detach_component and flow_recording_delete_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?

The description explains when to use it (inserting a reusable component reference) and how it differs from copying ('not copied — stays linked'). However, it doesn't explicitly name alternative tools or provide negative guidance about when NOT to use it, though the flow_recording_detach_component sibling clearly covers the inverse operation.

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