startRecording

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

No annotations are provided, so the description carries the full burden. It discloses one meaningful behavior ('Follows active tab automatically') and implies a continuous session with 'Use stopRecording to finish.' However, it does not mention prerequisites (e.g., whether enableRecorder must be run first), behavior if already recording, or any state changes beyond starting. This is a minimal but not empty disclosure.

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 three short, focused sentences: purpose, a behavioral trait, and a pairing instruction. Every sentence earns its place with no redundancy or filler, making it highly 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 simple start-recording tool, the description covers the core action and workflow. However, it lacks context about prerequisites (e.g., enableRecorder), error conditions (e.g., already recording), and what the tool returns. With no annotations and no output schema, these gaps make it adequate but incomplete.

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 description coverage is 100% for all three optional parameters, and the schema already provides clear descriptions for name, tags, and description. The description adds no additional parameter meaning, 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 opens with 'Start recording user actions,' a specific verb+resource that clearly states the tool's function. It distinguishes from sibling tools like stopRecording by referencing 'Use stopRecording to finish,' and the 'Follows active tab automatically' adds scope. This is strong clarity.

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 provides clear context: start recording, it follows the active tab, and you finish with stopRecording. This gives a basic workflow but does not explicitly exclude alternatives like enableRecorder or state prerequisites. It is clear but lacks explicit when-not-to-use guidance.

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