start_recording

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Start recording') but lacks details on permissions needed, whether recording is continuous or triggered, how to stop it (though 'stop_recording' is a sibling), error conditions, or what happens if already recording. This leaves significant gaps for a mutation tool.

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, efficient sentence that front-loads the core action and details the types of interactions recorded. There is no wasted text, and it directly communicates the tool's purpose without unnecessary elaboration.

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?

Given the tool's complexity as a mutation tool with no annotations and no output schema, the description is incomplete. It does not cover behavioral aspects like how recording works, what data is captured, or how to handle the recording state, which are critical for an agent to use this tool effectively in context with siblings like 'stop_recording'.

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 input schema has 100% description coverage, with the 'pageId' parameter documented as optional and defaulting to the active page. The description does not add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 clearly states the action ('Start recording') and the target ('user interactions'), specifying the types of interactions (clicks, scrolls, inputs). It distinguishes from siblings like 'stop_recording' by indicating the initiation of recording, but does not explicitly differentiate from other recording-related tools like 'start_console_capture' or 'start_network_capture' beyond the scope of interactions.

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?

No explicit guidance on when to use this tool versus alternatives is provided. The description implies usage for initiating interaction recording, but it does not mention prerequisites (e.g., whether a page must be active), exclusions, or comparisons to siblings like 'stop_recording' or other capture tools, leaving the agent to infer context.

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