execute_blender_code

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

Annotations already flag destructiveHint=true, so the risk profile is covered. The description adds useful operational details: the target port and the requirement to assign a result variable for return. It does not discuss side effects, timeouts, or error handling, but the annotation plus the brief operating note keep this at a median score.

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?

Two sentences with no filler; the primary purpose is front-loaded and the port and differentiation are each given one clause. Every sentence earns its place.

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 high-risk arbitrary-code execution tool with no output schema and minimal annotations, the description is thin. It omits return conventions beyond 'assign result variable', error handling, execution limits, and whether operations persist. An agent has enough to attempt a call but not enough to invoke it confidently in a production workflow.

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 schema provides zero description for the 'code' parameter, so the description carries the burden. It does specify allowed modules and the result-assignment requirement, which is genuinely useful. However, it never states the exact expected result variable name, return serialization, or how output/errors are delivered, so it only partially compensates for 0% coverage.

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 names a specific action ('Execute'), a clear resource ('arbitrary Blender Python (bpy, bmesh, mathutils)'), and a target ('SuperMCP port 9877'). It also distinguishes itself from Free's execute on 9876, so an agent can tell what it does at a glance.

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?

It provides context that this is the arbitrary-code path and explicitly separates it from Free's execute on 9876. However, it does not explain when to choose this over the many specialized Blender sibling tools (e.g., batch_execute_on_objects, mesh_operation), leaving usage largely implied.

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