set_shape_key_value

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

No annotations are provided, and the description carries no behavioral information at all. It does not disclose side effects, prerequisites (e.g., whether a shape key must exist), or return behavior. The description entirely fails to inform the agent.

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 this is under-specification rather than conciseness. A single phrase that repeats the tool name provides no value. It is not structured or front-loaded with any actionable content.

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?

With three required parameters, no parameter descriptions, no annotations, and a content-free description, the tool is completely inadequate for correct invocation. Even the existence of an output schema does not help because the agent cannot reason about inputs.

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%, so the description must compensate for the undocumented parameters. It does nothing. The parameter names (object_name, key_name, value) hint at meaning, but the description adds no types, formats, or constraints, leaving the agent guessing.

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 a literal restatement of the tool name: 'Blender Studio Pro MCP: set_shape_key_value'. It provides no verb, resource, or scope, and offers no differentiation from siblings like add_shape_key, list_shape_keys, or remove_shape_key. This 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 the many related shape key tools. No context, no alternatives, no exclusions. The agent has no way to determine the intended use case.

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