blender_mcp_edit_model

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

No annotations are provided, so the description carries the full burden. It describes the action as 'Send STL-edit instructions' but does not disclose whether the operation is destructive, whether Blender must be running, what happens on failure, or any side effects. The description is too vague for behavioral context.

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 sentence that efficiently conveys the core purpose without filler. Every word is necessary and front-loaded with the key verb and resource.

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 has 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return behavior, prerequisites (like Blender being running), or how it relates to the many sibling tools. A user would need additional knowledge to use it correctly.

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 each parameter having a description (e.g., 'Path to the local STL file', 'Ordered edit operations for Blender'). The tool description adds no extra meaning beyond summarizing the overall action. Baseline 3 is appropriate since schema already documents parameters thoroughly.

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 clearly states the action: 'Send STL-edit instructions to a Blender MCP bridge command for advanced model edits'. It identifies the specific verb 'send', the resource (STL instructions), and the context (Blender MCP bridge). This distinguishes it from sibling tools like specific edits (merge_vertices, center_model) or print tools.

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?

No guidance on when to use this tool versus alternatives. Siblings include specific STL editing tools (merge_vertices, center_model, lay_flat) and this is a general bridge for advanced edits, but the description does not explain scenarios or exclusion criteria.

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