cascadeur_list_scenes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful behavioral context by specifying that it lists only 'open scene tabs' and that the output includes 'current indices and names,' which goes beyond a generic 'list scenes' phrasing.

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 efficient sentence that front-loads the action and resource, then adds the two essential output components. There is no filler, redundancy, or unnecessary detail.

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 zero-parameter, read-only listing tool, this description is complete: it states the object being listed, the scope ('open'), and what information is returned ('current indices and names'). No output schema exists, but the description adequately covers the return contents. Annotations cover side-effect safety.

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 tool has zero parameters, so the schema leaves no ambiguity. With no parameters to document, the description does not need to add parameter-level meaning, and the 0-parameter baseline of 4 applies.

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 uses a specific verb ('List') with a precise resource ('open scene tabs') and names the key output details ('current indices and names'). It clearly distinguishes this tool from siblings like cascadeur_list_objects, cascadeur_list_actions, and cascadeur_list_tracks by scoping to scenes.

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 usage through its listing semantics: use this when you need to enumerate currently open scene tabs before targeting one by index or name. However, it does not explicitly state when to prefer this over alternatives such as cascadeur_status, cascadeur_get_state, or cascadeur_activate_scene.

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