start_recording

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

With no annotations, the description carries full burden. It only says 'Start recording' without revealing behaviors like whether it toggles, what happens to existing recordings, or if it requires specific track states. Minimal behavioral context is provided.

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 concise sentence. It is not verbose, but it lacks any structuring or additional context. Every word earns its place, but it could be more informative without becoming lengthy.

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?

Without output schema or annotations, the description is too minimal for a domain like Ableton where recording modes (session vs arrangement) and state dependencies matter. A more complete description would clarify the type of recording triggered.

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?

There are no parameters, and schema coverage is 100% trivially. The description adds no meaning beyond the schema, but this is acceptable given the absence of parameters. Baseline score of 3 applies.

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 recording' and the resource 'in Ableton'. It distinguishes from sibling tools like 'stop_recording' and 'toggle_session_record' by implying initiation, but does not specify recording mode (session/arrangement/overdub), which could cause ambiguity.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives like 'toggle_session_record' or 'set_overdub', nor does it mention prerequisites such as armed tracks or enabled overdub.

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