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

With no annotations, the description carries the full burden and does so thoroughly: it discloses the forced terminal 'aborted' state, the no-op for terminal replays, the watchdog timeouts, and the latency before flow_replay_status reflects the aborted state due to uninterruptible in-flight device calls. This is exceptional behavioral disclosure.

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 moderately long at five sentences, but every sentence contributes value: purpose, use case, watchdog context, no-op edge case, and status-lag caveat. It is front-loaded with purpose and usage, and the detail is justified for a tool with subtle behavioral side effects.

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 single-parameter, mutation-style tool with no annotations and no output schema, the description covers invocation source, side effects, timing, alternatives, and edge cases. An agent has everything needed to call it correctly and interpret the outcome.

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?

The schema already fully documents replayId as 'Replay ID returned by flow_replay_start or flow_recording_replay' with 100% coverage, so the description adds no new parameter semantics. It reinforces the ID origin but provides no additional format or type details beyond the schema.

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 opens with a specific verb+object ('Abort an in-flight replay') and names the exact originating tools (flow_replay_start, flow_recording_replay). It clearly differentiates from flow_replay_status by targeting the terminal 'aborted' state rather than polling indefinitely.

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 explicitly states when to use it: when a replay stops making progress (e.g., after a device/control-connection error) rather than polling flow_replay_status indefinitely. It also explains it is for cancelling sooner than the built-in watchdogs or cancelling a replay no longer needed, and documents the no-op behavior for already-terminal replays.

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