list_constraints

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses nothing about what the tool returns, whether it reflects currently-applied constraints, stale data, or any side effects. With a prefix-only description, the agent gets no behavioral context at all.

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 short, but this is under-specification rather than genuine conciseness. There is no informative content to be concise about.

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 1-parameter tool with an output schema that is not described anywhere, this description is completely inadequate. The agent cannot determine what it lists, what format the results take, or prerequisites for the object.

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 coverage is 0% for the single required object_name parameter, and the description does not compensate. The agent cannot tell whether object_name needs a Blender data path, a display name, or an index, and whether the object must already exist.

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 'Blender Studio Pro MCP: list_constraints' merely restates the tool name with a prefix. It does not state what is listed, on which object, or what a constraint is in this context. This is a tautology that adds zero semantic content.

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 is provided on when to use this tool versus alternatives. Siblings like add_constraint, remove_constraint, set_constraint_param, and add_bone_constraint exist, but the description offers no routing information.

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