set_scene_launch_quantization

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

Annotations only declare readOnly=false and destructive=false, leaving behavioral disclosure to the description. It adds useful behavior context with 'guarded', 'plan or apply', and the side-effect scope. It could spell out the confirmation-token flow more directly, but the schema property descriptions cover that aspect.

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 with no filler. The primary verb and object are front-loaded, and the second sentence adds only the necessary scope 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?

For a two-phase guarded mutation with no output schema, the description is nearly complete: it explains the operation mode, the source of identifiers, and the scope of the change. The plan/apply confirmation flow is left to the schema, but the schema documents it fully.

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?

The schema already documents all six parameters, so the baseline is 3. The description adds value by tying the operation to list_scenes and clarifying the per-scene versus global scope, which gives the parameters meaning beyond their raw schema descriptions.

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 operation and resource ('plan or apply a guarded per-scene clip-launch quantization override'), identifies the data source ('from list_scenes'), and clarifies the exact scope ('only the selected scene changes'). This clearly distinguishes it from global quantization or scene-launch siblings.

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 conveys when the tool is appropriate: for per-scene quantization overrides sourced from list_scenes, while explicitly noting the global setting is unaffected. It does not name specific alternative sibling tools, but the scope statement and schema details provide enough guidance for selecting this tool.

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