remove_shape_key

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

No behavioral information is disclosed. The description carries no details about side effects, permissions, safety, or return behavior. With no annotations to rely on, this is a critical gap.

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 extremely short but does not meet the threshold of conciseness—it is under-specification. While there is no waste, the lack of any meaningful content makes it inadequate.

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 tool with two required parameters and zero annotations, the description provides no context. An agent cannot determine how to call it correctly, what results to expect, or how it relates to sibling tools like add_shape_key or set_shape_key_value.

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%, and the description adds no meaning to the two required parameters (object_name, key_name). An agent has no clue what these parameters expect, formats, or valid values.

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 is only "Blender Studio Pro MCP: remove_shape_key", which is a direct restatement of the tool name. It provides no verb, resource description, or differentiation from siblings. It is a tautology.

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 alternatives. No context, no exclusions, no mention of prerequisites. The description offers zero situational direction.

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