recording_start

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

The description discloses a key behavioral trait: each recorded tool call gets a screenshot and annotated slide, which goes beyond the schema. However, with no annotations provided, it omits important context such as how recording is stopped, session requirements, or potential side effects, leaving the description to carry the full burden but only partially fulfilling it.

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, front-loaded sentence with no filler. Every word contributes to conveying the tool's purpose and core behavior, making it appropriately concise and well-structured.

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 tool with four optional parameters, no annotations, and an output schema, the description is too sparse to support fully correct invocation. It fails to explain parameter meanings, lifecycle details (e.g., how to stop recording), or how the recording session ties into the broader tool set, leaving significant 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?

The description does not mention any of the four parameters (window, display, output_dir, session_id), and schema description coverage is 0%, so no additional meaning is added beyond the bare parameter names and defaults. Agents receive no guidance on what these parameters do or how they affect recording.

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 a specific action ('Start') and resource ('automatic evidence recording'), and describes the outcome: each recorded tool call gets a screenshot and annotated slide. This distinguishes it from siblings like recording_stop and recording_capture, making its purpose unambiguous.

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 usage when you want to begin automatic recording, but it does not explicitly contrast with alternatives such as recording_capture or screenshot, nor does it mention prerequisites or when not to use the tool. The guidance is left to inference from the tool name.

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