set_constraint_param

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

Annotations are absent, so the description must carry the full burden of disclosing behavioral traits such as side effects, scene mutation, mode requirements, or reversibility. The description is silent on all of these, providing no behavioral transparency whatsoever.

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 a single sentence that merely restates the tool name and prefix. It is not concise in the sense of conveying useful information efficiently; it is severely under-specified. While it does not waste words, it also provides no content that 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?

Given the complexity of setting a constraint parameter and zero annotation or schema coverage, the description is completely inadequate. It omits essential context such as which object or constraint is affected, how the param/value pair works, and what the output schema represents. An agent cannot call this tool correctly based on the information provided.

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 has zero description coverage for all four parameters, and the description adds no meaning to param, value, object_name, or constraint_name. The agent is given no information about what values are valid, what the parameters represent, or how they relate to each other.

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 just a prefixed tool name ('Blender Studio Pro MCP: set_constraint_param') and provides no statement of what the tool does. It does not mention the action (setting a parameter on a constraint), the resource, or how it differs from similar tools like add_constraint or set_modifier_param. This is essentially a tautology of the tool's name.

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 any of the many sibling tools. No mention of prerequisites, context, or alternatives. An agent has no information about the typical use case or when it should be selected over other constraint or modifier tools.

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