obs-get-scene-item-source

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

No annotations are provided, so the description carries the full disclosure burden. "Gets" implies a read-only call, but the description says nothing about what is actually returned (a name string? a source object?), whether the scene item must exist, or what happens on invalid input. With no output schema either, this is a meaningful gap for a lookup tool.

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, which is good, but its brevity comes from under-specification rather than tight wording. It is front-loaded but conveys only the bare minimum.

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 lookup tool with no annotations and no output schema, the description should at least characterize the return value. Instead it leaves the shape of "the source" entirely unspecified and gives no hint about how sceneName/sceneUuid affect resolution.

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 description coverage is 100%, so the three parameters (sceneName, sceneUuid, sceneItemId) are already documented in the schema. The description adds no meaning beyond that, such as whether sceneName and sceneUuid are alternatives or whether sceneName is needed when the item ID is globally unique. Baseline 3 applies when the schema does the heavy lifting.

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?

"Gets the source associated with a scene item" names a verb (get) and a resource (source of a scene item), so the domain is identifiable. But "source" is undefined — it could mean the source name, ID, or full source object — and nothing distinguishes this from nearby siblings like obs-get-scene-item-id or obs-get-scene-item-private-settings.

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 guidance, no mention of prerequisites, and no reference to alternatives. The agent gets no help deciding between this tool and obs-get-scene-items or obs-get-scene-item-id.

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