add_collision

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. However, the description provides no information about side effects, required Blender state, return values, or whether it mutates the scene. The agent is left with no behavioral expectations.

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, not good conciseness. It is a single fragment that repeats the tool name. Every sentence should earn its place, but here there is not even a full sentence; no valuable information is conveyed.

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?

Even with an output schema present, the description is entirely inadequate. For a tool with one required parameter and no annotations, the definition fails to explain the tool's purpose, usage, or parameter semantics. The agent has no idea what 'add_collision' does, how to invoke it, or what to expect.

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 lists a single required parameter 'object_name' with no description, and schema description coverage is 0%. The description adds nothing about the parameter—what it refers to, its format, or its role. The agent has no way to construct a valid invocation beyond guessing the parameter is the name of a Blender object.

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 'Blender Studio Pro MCP: add_collision' which is essentially the tool name with a prefix, a tautology. It does not state any verb, resource, or scope beyond the name. There is no indication what 'collision' refers to in Blender (e.g., physics collision objects, collision shapes). It fails to distinguish the tool from any sibling.

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 or when not to. No alternatives are mentioned, and no context or prerequisites are provided. The description gives the agent zero basis to decide between this and any related tool.

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