back_to_arranger

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

The description discloses that it stops all session clips and resumes arrangement playback, which are important behavioral traits. Since no annotations are provided, this carries the full burden, and it does so adequately without contradicting any structured data.

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, front-loaded with the main purpose, and every word adds value. No wasted text.

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 parameterless tool with an output schema, the description fully covers the action's purpose and side effects. It is complete and leaves no ambiguity.

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?

There are no parameters (schema coverage 100% with empty schema), so the description adds meaning beyond the schema by explaining the action's effect. The baseline for zero parameters is 4, and the description meets it.

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 the tool switches playback from session view to arrangement, stops session clips, and resumes arrangement playback. It uses specific verbs and resources, distinguishing it from similar tools like 'session_to_arrangement' and 'start_playback'.

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 when to use the tool (when in session view and wanting to return to arrangement) by contrasting with session playback. It does not explicitly state when not to use it or name alternatives, but the context with sibling tools is clear.

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