blender_splatting

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

All annotations are false, leaving the description to carry the transparency burden. The description mentions 'cleaning them up,' which hints at modification, but it fails to disclose that operations like crop_and_clean may alter or delete splat data, nor does it explain export side effects or any prerequisites.

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 concise and well-structured, with the key term 'Gaussian Splatting' front-loaded. The only minor issue is the word 'Advanced,' which adds little substance, but overall it is efficient.

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 tool's complexity (14 parameters, 7-operation enum), the description is too sparse. It only covers import/cleanup/prepare, omitting operations like worldlabs, generate_collision_mesh, create_proxy, and optimize_for_vr. The output schema exists, but the description still leaves significant context unaddressed.

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 provides full descriptions for all 14 parameters (100% coverage), so the description adds no additional parameter-level meaning. This matches the baseline of 3, as the description does not need to compensate for schema gaps.

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 uses a specific verb+resource ('Gaussian Splatting management') and lists concrete actions (importing, cleaning, preparing for VR), which clearly differentiates it from sibling tools like blender_import or blender_mesh. It also names the target platform (Resonite), making the purpose unmistakable.

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 description provides clear context by mentioning hybrid environments and VR platforms, implying when the tool is useful. However, it does not explicitly state when to use this tool over alternatives or give any exclusions, so guidance is only implicit.

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