set_record_mode

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

Discloses that enabling alone does not record, and repeating state has no effect, confirming idempotentHint annotation. No contradiction with annotations.

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 sentences: front-loaded with main action, then parameter explanation, then usage guidance. 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?

Given the tool's simplicity (1 bool param, output schema exists), the description fully covers behavior, usage, and constraints. No gaps.

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?

Input schema has 100% coverage with description for the single boolean parameter. Description adds 'true enables recording; false disables it' but mostly repeats schema info. Baseline 3 adequate.

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?

Clearly states it arms or disarms Live's global Arrangement Record state, with specific verb+resource. Distinguishes from sibling tools like set_session_record and trigger_session_record.

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?

Explicitly tells when to use this tool (for Arrangement Record) and when to use alternatives (set_session_record/trigger_session_record for Session slots). Also explains prerequisites (arm tracks, start playback) and idempotency.

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