trigger_session_record

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

No annotations are provided, so the description carries full burden. It states what is recorded but does not disclose whether the action toggles or starts a mode, whether it overwrites existing arrangement data, or any state assumptions. Behavioral traits like side effects or prerequisites are missing.

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?

Three concise sentences that are front-loaded with the action. Every sentence adds value: states the action, specifies what it records, and gives a real-world use. No wasted words.

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?

Despite having zero parameters and an output schema (not shown), the description lacks key context: whether the recording is modal or one-shot, what happens to existing arrangement clips, or what the return value indicates. For a simple tool, more behavioral context is needed.

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 (0 params, schema coverage 100%). Baseline for zero parameters is 4, but the description adds no extra meaning beyond the name besides a specific use case. It does not provide additional context about the action's behavior.

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 'Session Record mode', and explains what it does: records session view clip launches and parameter changes into arrangement view. It distinguishes itself from siblings like 'set_session_record' by focusing on capturing real-time performances.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'set_session_record' or 'set_arrangement_overdub'. It implies use for capturing performances but lacks context on when not to use it or what distinguishes it from similar tools.

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