session_record_start

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only lists what events are captured; it does not mention that recording is an ongoing stateful operation, whether a returned sessionId is needed later, how to stop the recording, or any side effects on the page or browser.

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 a single focused sentence that front-loads the action and resource and packs the relevant event scope into a short list. Every word contributes value with no filler.

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 state-changing tool with no annotations and no output schema, the description is too thin. It omits the recording lifecycle (that recording persists until stopped), the need for a sessionId in later operations, and any prerequisite such as session_install. The sibling names hint at the workflow, but the description itself leaves those gaps.

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?

All three parameters are already fully described in the schema with 100% coverage, including defaults and optionality. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.

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 specific verb and resource — "Start recording user interactions on a tab" — and enumerates the captured event types (clicks, scrolls, keystrokes, form fills, navigations). This makes its purpose immediately clear and distinguishes it from sibling tools like session_record_stop and session_record_events.

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 start verb implies this tool is used to begin a recording session, but the description gives no explicit guidance about when to use it versus related tools such as session_install, session_record_stop, or session_record_replay. Usage context is inferred from the tool name and siblings rather than directly stated.

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