back_to_arranger

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

The description explains the behavioral state (orange 'Back to Arrangement') and the action of returning control, which adds value beyond the annotation 'destructiveHint=false'. It does not contradict 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?

The description is a single, clear sentence that immediately states the purpose and context. Every word is necessary and earns its place.

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 has no parameters and an output schema exists, the description adequately explains the purpose and usage context. It could optionally mention that the action is reversible, but it is sufficient as is.

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, and schema coverage is 100%. The description does not need to add parameter information; a baseline of 4 is appropriate.

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 action (return playback control to the Arrangement) and specifies the resource (Arrangement) and the context (after Session clips have overridden arrangement content, the orange state). It distinguishes itself from siblings like 'switch_to_arrangement_view' by focusing on control return rather than view switching.

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 provides clear context for when to use the tool (after Session clips have overridden arrangement content). However, it does not explicitly state when not to use it or mention alternatives, though the context is sufficient for an informed decision.

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