List scenes

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds what the response contains (scenes in OBS order, the current program/preview scene, and optionally per-scene sources), which goes slightly beyond the annotations, but it says nothing about pagination, error behavior, or connection requirements.

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?

A single short sentence with no filler, and the most important content (scene listing and order) is front-loaded. It is efficiently sized for a one-parameter read 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?

With no output schema, the description carries the burden of describing returns, and it partially does so (order, program/preview scene, optional sources) but leaves the actual field names and shape unspecified. For a simple listing tool it is adequate but not 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?

Schema coverage is 100% and the single parameter includeItems is fully documented in the schema. The description's 'optionally the sources in each scene' mirrors that same meaning without adding format or default nuance, so the baseline 3 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 names the resource (scenes) and what the listing contains, but it is a verbless noun phrase that essentially restates the tool name 'list_scenes' and the title. It conveys scope (OBS order, current program/preview scene, optional sources) but never states the action, so an agent must infer 'list' from the name alone.

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?

There is no when-to-use or when-not-to-use guidance and no mention of the obvious alternatives among siblings such as get_overview or switch_scene. A read-only listing tool is fairly self-evident, but the description provides no routing context.

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