trigger_session_record

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

Annotations indicate destructiveHint=false, so the tool is non-destructive. The description adds valuable behavioral details: it records into armed tracks, uses record_length for a fixed-length loop, and auto-switches to playback. This goes beyond the annotation alone.

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 sentence that efficiently conveys the tool's purpose, parameter usage, and behavior. Every word adds value, and it is front-loaded with the key action.

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 tool with one optional parameter and an output schema (though not shown), the description adequately explains the recording behavior and parameter. It could mention what happens if record_length is null (continuous recording), but the example implies it.

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 schema has 0% description coverage, so the description compensates by explaining that record_length is in beats and provides an example (16.0 = 4 bars) for a fixed-length loop. This adds clear meaning beyond the schema type definition.

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 that the tool starts session recording into armed tracks and explains the record_length parameter for a fixed-length loop. However, it does not explicitly differentiate it from sibling tools like set_record_mode or set_session_record, which could also be related to recording.

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 implies usage when starting a fixed-length recording but does not provide explicit guidance on when to use this tool versus alternatives (e.g., set_record_mode for manual stop). No when-not-to-use or prerequisites are mentioned.

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