set_scene_musical_context

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

Annotations already declare non-read-only, non-destructive, non-idempotent and open-world behavior. The description adds genuine semantic context beyond them: disabled overrides inherit the song context, while enabled overrides only take effect at scene launch, explaining the deferred effect of the write.

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?

Two sentences, zero filler, and the plan-or-set scope is front-loaded ahead of the behavioral clarification. Every clause 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?

With no output schema and a 10-parameter mutation tool, the description covers purpose and override semantics adequately, and the token/plan-hash mechanics are handled in the schema. It omits that a real apply requires a confirmation token, but that detail is covered by the parameter descriptions.

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 coverage is 80%, so the baseline is 3. The description goes slightly beyond by explaining what the enable flags actually do (inherit vs. apply at launch), giving meaning to tempoEnabled and timeSignatureEnabled that the schema descriptions do not.

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 states a specific verb+resource: planning or setting a scene's tempo and/or time-signature override. The 'Session scene' qualifier distinguishes it from the song-level set_song_musical_context, though no sibling is named explicitly.

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?

'Plan or set' implies the two-phase dry-run/apply workflow, and 'takes effect when the scene is launched' hints at the operational context. However, it never states when to choose this over set_song_musical_context or set_tempo, leaving the routing to inference.

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