obs_list_sources_in_scene

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only list operation and enumerates the returned data (item IDs, visibility, transform). It does not mention behavior for nonexistent scenes, but the core behavior is transparent.

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: the first states purpose and output fields, the second gives a usage hint. Every word earns its place, with no 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 simple list tool with one parameter and no output schema, the description adequately covers purpose, key output fields, and usage context. It lacks details on return format or edge cases, but these are not critical for such a tool.

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 only parameter sceneName is fully documented in the schema with 'Scene to inspect.' The description adds the context that the scene contains sources, but does not significantly enhance the semantics beyond what the schema provides. Given 100% schema description coverage, 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 uses the specific verb 'List' with resource 'sources (scene items) inside a scene' and explicitly states the output fields (item IDs, visibility, transform). This clearly differentiates it from sibling tools like obs_list_inputs and obs_list_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 phrase 'Needed before moving, resizing or hiding anything' gives explicit context for when to use this tool. It implies a relationship with modification tools like obs_set_source_transform and obs_set_source_visible, though it does not name alternative tools explicitly.

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