blender_refine_get_session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only confirms a read operation and names the data categories returned ('details and iteration history'), without revealing response shape, iteration-history ordering, error behavior for an invalid session_id, or whether an active session is required.

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?

A single front-loaded sentence with zero filler — the verb and resource appear immediately. It is efficient, though slightly more contextual detail could have been added without sacrificing conciseness.

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?

With no output schema and no annotations, the description is the agent's only source for what 'details' and 'iteration history' actually contain. The text is too thin: the agent cannot predict the response structure, the outcome of a bad session_id, or how to obtain a valid session_id (e.g., from create_session or list_sessions).

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%, with session_id already documented as 'Refinement session ID,' so the schema carries the parameter meaning. The description adds nothing about where to obtain a session_id or what format it takes, so the baseline 3 applies.

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 states a specific verb ('Get'), a clear resource ('a refinement session'), and a defined scope ('details and iteration history'). It is clearly different from siblings like blender_refine_create_session, blender_refine_list_sessions, and blender_refine_iteration, though it never names them explicitly.

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 gives no guidance on when to use this tool versus blender_refine_list_sessions, blender_refine_iteration, or blender_ai_refine. There are no exclusions, prerequisites, or mentions of alternatives; the agent must infer usage purely from the tool name.

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