set_scene_item_blend_mode

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

With no annotations, the description must carry the full behavioral disclosure burden. It only states the action without detailing error behavior, prerequisites, idempotency, or side effects. For a mutation tool, this lack of transparency is a notable gap.

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 concise and uses a clear Args structure. Every sentence adds value, though the blend_mode enumeration could be slightly more explicit with the full 'OBS_BLEND_' prefix on each option. No unnecessary fluff.

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 setter with no output schema, the description covers the essential parameters but omits contextual details such as return behavior, error conditions, or whether the scene item must already exist. It is adequate for basic use but not fully 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?

The input schema provides zero parameter descriptions (0% coverage), so the description's Args section compensates well by explaining each parameter. Notably, it enumerates the allowed blend_mode values, adding meaning beyond the bare schema titles and types.

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 starts with 'Set a scene item's blend mode' which uses a specific verb and resource, clearly distinguishing it from the sibling get_scene_item_blend_mode. It leaves no ambiguity about what the tool does.

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 description implies usage by the verb 'Set' but provides no explicit guidance on when to use it vs alternatives, prerequisites, or exclusions. It does not mention that reading the blend mode is available via a sibling tool, leaving usage context to inference.

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