set_session_mode_tool

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

No annotations are present, so the description carries the full burden. It states the action ('Set') but not what changes, side effects on audition/playback, prerequisites like an open project, or persistence. This is a significant gap for a mutation tool.

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?

A single front-loaded sentence with zero filler; the allowed values are packed efficiently into the same sentence.

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 has an output schema, but with no annotations and no explanation of behavioral effects, the description is only minimally adequate for an agent to call it confidently. It covers the valid mode values but not the broader implications of switching modes.

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. It does for `mode` by listing the allowed values, but `project_path` is left entirely to its title, so the description only partially compensates.

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 names a specific verb ('Set') and resource ('DAW audition mode') and enumerates the exact accepted values (mix, fx, raw). It clearly distinguishes this from sibling session/playback tools like set_session_playing_tool.

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 operation is unambiguous: use it when you need to set the DAW's audition mode. It doesn't explicitly name alternatives or exclusions, so it doesn't earn a 5, but the context is clear enough among the set_session_* siblings.

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