get_scene_list

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

No annotations provided, so the description carries the full behavioral burden. It's a read/query operation by nature ('Get list'), but nothing is disclosed about whether it requires a live OBS connection, whether it can fail when OBS is offline, what happens if no scenes exist, or whether the list is cached or real-time. For a state-querying tool with zero annotation coverage, more disclosure is warranted.

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?

Single sentence, zero waste. It communicates the core function in minimal words, which is entirely appropriate for a zero-parameter list tool.

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 simple list-returning tool with no parameters and no output schema, the description is mostly adequate. However, there's no output schema, so the tool doesn't explain what the returned list contains (scene names? objects with properties? ordering?). Without an output schema and with siblings like get_obs_health and get_current_show_state, some detail about what fields/format the scene list returns would improve completeness.

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 zero parameters, so the description carries no parameter burden. Baseline of 4 applies for a 0-parameter tool. Nothing to add beyond what the schema already conveys.

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?

Clear verb+resource ('Get ... list ... scenes') and states it lists available scenes. It distinguishes from siblings like get_current_show_state, which returns show state rather than scene availability. Purpose is clear but doesn't elaborate on what 'available' means or what the returned scene details contain.

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?

No guidance on when to use this tool vs alternatives like set_scene or get_current_show_state. The description doesn't clarify whether this is a pre-broadcast discovery step, whether it pairs with set_scene for selection, or how it differs from getting the current scene. No when/when-not guidance provided.

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