obs-get-scene-item-blend-mode

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

No annotations are provided, so the description carries the full behavioral burden. It does not state the return format (e.g., the blend mode enum values), what happens if the scene item ID is invalid, or whether the scene must be active. For a read tool with zero annotation coverage, that leaves meaningful gaps.

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 front-loaded sentence with no wasted words. It is efficient for a simple getter, though it is so terse that it sacrifices context that would have been cheap to add.

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 getter with a fully documented schema and no output schema, the description is minimally adequate. However, it should give some hint about the returned blend mode values or error behavior to be complete for an agent that cannot see an output schema.

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%, and all three parameters (sceneName, sceneUuid, sceneItemId) are documented in the schema. The description adds no parameter meaning beyond that, so the baseline of 3 is appropriate.

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 states a specific verb ("Gets") and resource ("blend mode of a scene item"), which lets an agent distinguish it from the sibling setter obs-set-scene-item-blend-mode. It doesn't explicitly name the sibling, but the get/set pairing is unambiguous from the name and verb.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites. The read-only nature is implied by "Gets" but the description never says an agent should call this to inspect a scene item's composite behavior before modifying it.

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