Export Session Recording

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

Discloses that it creates a JSON script from mutating actions with @eN refs resolved to stable selectors. No annotations provided, so description carries full burden. However, it does not mention idempotency, side effects, or whether it modifies the session.

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?

Two concise sentences, no wasted words. Front-loaded with purpose and key details. Clear structure.

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?

No output schema, so description should explain return value. It does not describe the structure of the exported recording or the JSON script. Also missing prerequisites like session existence. Adequate but leaves gaps for an 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 covers all parameters with descriptions (100% coverage). Description adds value by explaining the specific role of the 'format' parameter and its compatibility with the execute tool, but no extra detail for other parameters.

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?

Clearly states it exports session action history as a replayable recording, with two distinct output formats. Differentiates from siblings like session_export_trace and session_replay by specifying 'action history' and 'replayable recording'.

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?

Provides explicit guidance to use format='playwright' for Playwright scripts compatible with execute tool. Implicitly suggests when to use each format, though lacks explicit when-not-to-use or alternatives.

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