Call Blender Tool

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

With no annotations at all, the description carries the full behavioral burden, yet it discloses nothing beyond the word "approved." It does not say what happens with an unapproved name, whether executed commands can modify or destroy data in the scene, whether an active session is required, or how failures are reported — all essential for an arbitrary dispatcher.

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 single front-loaded sentence contains no filler, but its brevity comes at the cost of under-specification rather than efficiency; one or two more sentences about command discovery and params would earn their 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 generic dispatcher with a free-form nested params object, zero annotations and no output schema, the definition is far too thin — it omits discovery workflow, side-effect profile, and error behavior that an agent needs before invoking arbitrary scene commands.

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 0% for both parameters, so the description must compensate and does not. It never explains that "name" must match an entry from list_blender_tools, nor that "params" is validated against that command's own signature — a serious gap given the untyped nested object.

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 gives a verb and resource ("Call one approved ViperMesh Blender command") and the word "one" faintly distinguishes it from call_blender_tool_batch, but it never explains what a "command" is or where valid command names come from (presumably list_blender_tools). An agent still cannot tell from the description alone how this differs from run_blender_scene_stage or the batch sibling.

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?

There is no guidance on when to use this tool versus call_blender_tool_batch or run_blender_scene_stage, and no mention of prerequisites such as establishing a session or discovering approved command names first. Usage is only inferable from the name.

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