blender_scene_switch

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

Annotations indicate idempotentHint=true and destructiveHint=false, but the description adds no extra behavioral context beyond the action itself. It doesn't disclose side effects, error handling, or what happens if the scene name is invalid, so it fails to enhance transparency beyond what annotations already provide.

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 very concise with only one functional sentence, and it front-loads the purpose. However, the 'Returns' section is vague ('Switch result') and could be omitted or clarified. No unnecessary words.

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 tool with annotations and an output schema, the description is minimally adequate. It covers the core action but omits details like error conditions (e.g., nonexistent scene) or behavior when switching to the current scene. It lacks completeness for edge cases.

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 already defines 'scene_name' with a description 'Name of the scene to switch to,' which is more informative than the description's 'Target scene name.' Since schema description coverage is effectively low (0% as per context), the description should compensate, but it does not add value.

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 clearly states 'Switch to the specified scene,' which uses a specific verb ('switch') and resource ('scene'). This distinguishes it from sibling tools like blender_scene_create, blender_scene_delete, and blender_scene_list, which have different purposes.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention when not to use it or any prerequisites (e.g., ensuring the scene exists). It only describes the action without contextual usage advice.

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