session_record_replay

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

With no annotations, this description carries the full burden, and it only conveys that replay targets the original tab. It does not disclose side effects on the tab/browser, whether the replay requires an explicit stop first, how speed affects playback, or what happens after replay completes.

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?

A single, front-loaded sentence with no filler, and the key qualifiers ('stopped', 'original tab') are packed in. It earns a high conciseness score, though brevity comes at the cost of missing behavioral and parameter detail.

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 action-oriented, has no annotations, and has no output schema, so the description should supply the missing behavioral and return context. It does not explain return type, tab state after replay, errors for an invalid session, or the speed parameter's effect — leaving the definition under-specified for a new agent.

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 describes the speed parameter (default 1), but sessionId, the only required parameter, has no schema or description explanation. The tool description adds no parameter-level meaning, so an agent must guess that sessionId refers to a previously recorded session ID.

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 uses a concrete verb-resource pair ('Replay' + 'stopped recording session') and adds a scope qualifier ('in the original tab'). This distinguishes it from the recording-management siblings like session_record_start/stop/list/events, even though it never names them.

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 implies the intended use — replaying a session after it has been stopped — but it never states when to prefer it over related tools or lists any exclusions. The 'stopped' qualifier hints at a precondition, but alternatives and non-use cases are left unspoken.

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