start_recording

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

With no annotations and only a two-word description ('Start recording'), the tool's behavior is entirely undisclosed. It does not mention transport state changes, whether recording is non-destructive, what happens to existing clips, or any side effects. This is a minimal disclosure that fails to inform the agent of important behavioral traits.

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 short sentence that is front-loaded and free of fluff. For a zero-parameter action, this is appropriately concise, though it sacrifices useful detail for brevity.

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 simplicity, the description is still incomplete in context. It fails to disambiguate from sibling recording controls, explain what 'recording' means here, or describe expected behavior. The lack of annotations and output schema means the description carries full responsibility, which it does not fulfill.

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, so the baseline is 4. The description adds no parameter-specific information, but none is needed since the schema declares an empty properties object. The input schema fully covers parameter expectations.

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 states a clear action ('Start recording') and resource ('Ableton'), but it does not specify whether this starts session recording, arrangement recording, or a general transport record. Sibling tools like toggle_session_record, toggle_arrangement_record, and stop_recording highlight this ambiguity, making the tool's exact purpose unclear.

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 guidance is provided on when to use this tool versus alternatives such as toggle_session_record, toggle_arrangement_record, or capture_midi. The description gives no context about prerequisites (e.g., armed track) or situations where this tool is the preferred choice.

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