set_record_mode

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

With no annotations provided, the description carries the full burden. It says 'toggle', but the parameter 'enabled' indicates a set operation. It does not disclose side effects, such as interactions with overdub or punch-in modes, or whether it clears or preserves other settings.

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 extremely concise (two words plus context). While brevity is generally good, it sacrifices clarity and completeness. The term 'toggle' is ambiguous.

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 simple nature (one boolean parameter) and the presence of an output schema, the description could still provide more context about expected behavior, such as what 'arrangement record mode' means and how it relates to other record modes. It lacks integration with the sibling tools.

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?

Schema description coverage is 0%, so the description must compensate. The description only repeats the tool's purpose and does not explain what 'enabled' means or its effect on recording state. It adds minimal value beyond the parameter name.

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 'Toggle arrangement record mode' specifies the tool's action and the target ('arrangement record mode'). However, 'toggle' is slightly misleading as the tool likely sets a state via the 'enabled' parameter rather than toggling. It distinguishes from 'set_session_record' by specifying 'arrangement', but could be clearer.

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 guidance on when to use this tool versus alternatives like 'set_session_record' or 'trigger_session_record'. The description does not mention prerequisites or context for use.

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