get_scene_item_blend_mode

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

With no annotations, the description carries the full burden. It only states that it gets a value, with no disclosure of side effects (likely none), return behavior (e.g., what happens if scene_item_id doesn't exist), or any special conditions. This is minimal but not misleading.

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 a single, front-loaded sentence and is concise. However, it is perhaps too terse, lacking helpful context, but it earns points for brevity and clarity.

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 tool with 2 parameters and no output schema, the description is incomplete. It does not indicate expected return values, error conditions, or parameter specifics. The sibling tool 'set_scene_item_blend_mode' exists, but no relationship is mentioned.

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 0%, so the description must compensate. It does not explain the parameters 'scene_name' or 'scene_item_id' beyond their names, and the names alone may not be enough for an agent to understand required context (e.g., item IDs may be scene-relative). No parameter details are provided.

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 'Get a scene item's blend mode.' clearly states the action (get) and the specific resource (scene item's blend mode). It distinguishes from the sibling tool 'set_scene_item_blend_mode' which performs the write operation.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it complements the setter, nor does it provide any context on when retrieving a blend mode is appropriate.

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