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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds value beyond them: it discloses the returned fields, the deletion-guard relationship, and an authentication/ownership requirement ('must be a fragment owned by the authenticated user').

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?

Four tight sentences, front-loaded with the core action, then purpose, then return shape, then constraint. No filler; each sentence contributes distinct information.

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 read-only single-parameter query whose annotations already cover safety, the description supplies everything needed: the action, its purpose, the return fields (compensating for the absent output schema), and the ownership precondition. Nothing material is missing.

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 the single componentId parameter is already documented, setting a baseline of 3. The description goes further by constraining the parameter's validity (it must be a fragment owned by the authenticated user), adding meaning beyond the schema's generic 'recording ID' phrasing.

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?

States a specific verb (List) and resource (test steps referencing a component via a live COMPONENT_REF), which clearly distinguishes it from sibling mutation tools like flow_recording_insert_component or flow_recording_detach_component. An agent knows exactly what this returns without opening the schema.

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?

Explains the operational context well: it 'backs the deletion guard,' implying you call it to check whether a component is safe to delete. However, it does not explicitly name alternative tools or state when-not-to-use, so the routing is implied rather than spelled out.

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