Start recording

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

With no annotations, the description carries the behavioral burden. It goes beyond the name by disclosing 'only when stopped' (a guard condition) and 'then verify recording state' (a post-action verification step). This provides useful transparency, though it omits potential failure modes or what happens if the precondition fails.

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 that efficiently communicates the action, precondition, and verification. Every word earns its place with no redundancy.

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 zero-parameter, simple action tool, the description provides adequate context: what it does, when to use it, and a post-condition. It doesn't describe error handling or return values, but given the tool's simplicity and the strong sibling context, this is a minor gap.

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 tool has zero parameters and the schema is empty (100% coverage), so the baseline is 4. The description adds no parameter details, which is appropriate since there are none to document.

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 verb 'Start' and the resource 'local recording', and the phrase 'only when stopped' adds a specific condition. It distinguishes from sibling tools like studio_stop_recording and studio_start_live by specifying 'local recording' and the precondition.

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 explicit guidance: 'only when stopped' is a clear when-not condition, implying the tool should not be called if recording is already active. It also distinguishes 'local recording' from live streaming, offering context for when to use this tool over studio_start_live, though it does not explicitly name alternative tools.

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