blender_msfs_create_collision_convex

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 explaining side effects. It only says it creates a convex hull collision mesh; it does not say whether a new object is created, whether the source object is modified, whether existing collision data is replaced, or how collision_type is applied. For a mutation tool, this is a significant transparency 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 a single front-loaded sentence with no filler. 'Create a convex hull collision mesh' states the action and resource immediately, and the parenthetical adds only the differentiating tradeoff.

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 no annotations and no output schema, the description alone must enable correct selection and invocation among closely related siblings like create_collision_box, create_collision_mesh, and tag_collision_type. It does not explain when this particular hull type should be created, what happens to the source object, or the meaning of collision_type choices, so key context is missing.

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 100%, so the schema already documents object_name and collision_type, including the enum values. The description adds no per-parameter detail, such as how collision_type affects the generated hull or which value is appropriate in which scenario, so it stays at the baseline.

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 states a specific verb ('Create') and a specific resource ('a convex hull collision mesh'), and the 'convex hull' qualifier plus the accuracy/performance balance distinguishes this from the sibling collision tools like create_collision_box and create_collision_mesh. An agent can tell what this tool does without needing to open the schema.

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?

The parenthetical '(balance between accuracy and performance)' implies this is a middle-ground option compared to box or full mesh collisions, but it does not explicitly state when to choose this over those alternatives or when not to use it. The guidance is contextual but left to inference rather than clearly stated.

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