create_scene

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

The annotations (all false) indicate this is a mutation but not destructive. The description adds the return format but does not disclose other behavioral traits like what happens if the scene name already exists, whether the new scene becomes active, or any side effects. This is some added value over annotations but not comprehensive.

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 succinct and well-structured: a clear first sentence stating purpose, a return format note, and a practical example. Every sentence adds value, with no redundant or verbose wording.

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?

While the tool is simple and has an output schema, the description leaves gaps about important edge cases and side effects, such as behavior when the scene name already exists or whether the created scene is set active. Given sibling tools like set_active_scene, this context would improve completeness.

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 has scene_name with a default but no description (coverage 0%). The description clarifies that the name is used for the new scene and provides a concrete example ('MyScene'), effectively compensating for the schema's lack of parameter documentation.

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 that the tool creates a new Blender scene with a specified name, using a specific verb ('Create') and resource ('Blender scene'). This unambiguously distinguishes it from sibling tools like list_scenes, set_active_scene, and clear_scene.

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 usage context is implied: you use this when you need a new scene. However, it does not explicitly mention alternatives or when not to use this tool (e.g., when you need to switch active scene, use set_active_scene). There is no explicit when-to-use vs alternatives guidance beyond the apparent purpose.

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