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

With no annotations, the description carries the full burden. It discloses the core behavioral traits: replaces the live reference, deep-copies steps, drops linkage, and limits depth to one level. It also states the ownership prerequisite. It doesn't mention reversibility or error handling, but the essential side effects are well covered.

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 focused sentences with no filler. The primary action and effect are front-loaded, constraints follow naturally, and every sentence contributes meaning.

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 mutation with no output schema, the description explains the transformation, the limitation, and the ownership requirement. It omits potential error conditions or return behavior, but an agent has enough to understand the action and its consequences. This is near-complete for the tool's complexity.

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% (both parameters have descriptive text), so the description adds little beyond the schema. It does reinforce that stepIndex refers to a COMPONENT_REF step and that recordingId is the test ID, but no additional semantics or formatting details are provided.

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 states a precise action (detach/materialize a component reference), the target resource (a test's COMPONENT_REF step), and the outcome (replaces it with a deep copy and drops linkage). It clearly distinguishes from siblings like flow_recording_insert_component and flow_recording_replace_step by focusing on breaking propagation.

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 clear context on when to use the tool (when you want to make component steps private and editable without affecting the component) and key constraints (one-level only, ownership requirement). However, it doesn't explicitly contrast with alternatives or state when not to use it, though the purpose is fairly self-evident.

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