blender_refine_create_session

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It confirms that a session is created and that it tracks iterative improvement, but it does not explain what a session is, whether it creates Blender-side state, what it returns, or how it relates to subsequent iteration calls.

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 with no filler or repetition. It is concise, though the conciseness leaves out important behavioral and usage context.

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?

This is a stateful session-creation tool with no annotations and no output schema, yet the description only provides a one-line purpose. It does not explain the session lifecycle, prerequisites, how prompt/reference_image are used, or what the agent should do after creating the session, making it incomplete for reliable invocation.

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%, so the schema already documents all three parameters. The description adds no additional meaning about how 'prompt', 'object_name', or 'reference_image' are used in the session, but it is not required to compensate for a coverage gap.

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 uses a specific verb ('Create') and resource ('a new refinement session') plus a clear goal ('track iterative improvement of a 3D model'). It is distinguishable from the sibling tools like blender_refine_iteration and blender_refine_list_sessions, though it does not explicitly contrast itself with them.

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 phrase 'to track iterative improvement' implies that this tool is for starting a session in an iterative refinement workflow, but it does not explicitly say when to use it versus alternatives like blender_ai_refine, or state that iteration calls should follow session creation. The usage context is implied rather than explicit.

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