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

Annotations already declare destructiveHint=true and non-idempotent, so the bar is lower, yet the description adds real substance: it specifies that steps and meta are overwritten from the snapshot, that snapshots are written on every mutating save with a 10-version retention window, and that ownership is required. It omits whether the revert itself produces a new snapshot (i.e. whether it is undoable), which keeps it from a 5.

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, front-loaded with the action and its effect, then retention policy, then auth and error behavior. No filler; each sentence adds a distinct operational fact.

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?

With no output schema, the description carries the return/error burden and does mention not-found behavior for both unknown recording and version. It leaves a small gap around whether the revert is itself snapshotted or reversible, which matters for a destructive operation.

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 baseline is 3, but the description adds meaning beyond the schema: 'version' is bounded by the 10-version snapshot retention policy, and 'recordingId' must belong to the authenticated user. This gives the agent practical bounds on valid inputs.

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 (revert) and resource (test recording) plus exactly what is restored: steps and meta (name/category/tags). This clearly separates it from siblings like flow_recording_save, flow_recording_get, and flow_recording_replay without needing to open a 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?

Gives clear context for when the tool applies (restoring a previously saved version) and states the ownership prerequisite and that unknown recording/version returns not-found. It stops short of naming explicit alternatives or when-not-to-use cases, e.g. inspecting the current state with flow_recording_get before reverting.

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