blender_session

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

The description reveals key behavioral details beyond the annotations (all false), such as 'stop: kill the managed Blender GUI process' and the bridge addon requirement for run_script. This provides helpful context about side effects and prerequisites. No contradictions with annotations were found.

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 well-organized bulleted list with clear sub-points. Each line serves a purpose: defining the tool's scope, listing operations, and noting prerequisites. There is no redundancy or filler, making it efficient and easy to scan.

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?

Given the tool's multi-operation complexity, the description covers all operations, their parameters, and the bridge addon prerequisite. An output schema exists, so return value details are not needed. Minor gaps such as error handling or behavior when Blender is not running are not addressed, but overall completeness is adequate.

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 provides operation-specific descriptions for every parameter (100% coverage). The description adds value by listing the available demo names for demo_name and grouping parameters by operation, which helps disambiguate. However, it does not drastically enrich parameter meaning beyond the schema's existing descriptions.

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 begins with 'Manage a Blender GUI session from the MCP server', which is a specific verb+resource statement. It then lists five distinct operations (status, start, stop, run_script, demo), making the tool's scope unambiguous. Although it doesn't explicitly differentiate from siblings, the operation list clearly distinguishes it from single-purpose tools like blender_render or script_execute.

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 implies when to use the tool by enumerating operations, but it does not explicitly state when to prefer this tool over alternatives such as script_execute or blender_status. It does provide a useful prerequisite for run_script (bridge addon enabled), but lacks exclusionary guidance or reference to sibling tools.

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