get_scene_list

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

With no annotations, the description must convey behavior on its own. It clearly states a read-only list operation, but it does not clarify whether it operates on the current scene collection, nor does it describe the exact return structure beyond scene names and program/preview names. It lacks any note about side effects or error behavior.

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 one sentence, front-loaded with the main action, and every word is necessary. Zero fluff.

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 0-param, no-output-schema tool, the description covers the return values (every scene, current program and preview scene names) and is sufficient. Minor gap: it doesn't specify 'current scene collection' context, but this is inferable from the sibling tools. Given the minimal complexity, it is nearly complete.

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 0 parameters, so the baseline is 4. The description makes no parameter claims, and there is nothing to compensate for.

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' and identifies the exact resource: every scene, plus the current program and preview scene names. This clearly distinguishes it from sibling tools like get_current_program_scene or get_scene_collection_list, which have narrower or different scopes.

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 the tool is used to retrieve a full scene list with the current program/preview names, but it does not explicitly discuss when to use this tool versus alternatives such as get_current_program_scene or get_current_preview_scene. No exclusions or alternative recommendations are provided.

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