set_record_mode

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

Annotations already indicate non-destructive (destructiveHint false). The description adds that start_playback records armed tracks when record_mode is on, providing some behavioral context. However, it omits details like permissions, return behavior, or side effects.

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 two sentences with no fluff. It front-loads the purpose. However, the first sentence could be more precise by using 'Set' instead of 'Toggle' to match the parameter.

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?

The tool is simple, and an output schema exists (not shown), so return info isn't required. However, the description does not mention prerequisites (e.g., armed tracks, playback state) or the exact relationship with start_playback, leaving some gaps for a recording tool.

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 input schema has a single boolean 'enabled' with 0% description coverage. The description says 'Toggle' but the parameter implies setting a state, causing confusion. It does not clearly define what 'enabled' means or how it maps to toggling 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 it toggles Arrangement record and explains the effect on start_playback. It distinguishes from sibling tools like set_session_record or trigger_session_record by specifying the context ('Arrangement'). However, it uses 'Toggle' while the parameter is 'enabled', creating slight 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?

The description explains when to use it (to enable recording via start_playback) but does not explicitly mention when not to use or suggest alternatives among numerous recording-related sibling tools like set_session_record or trigger_session_record.

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