Create Gaussian Splat scene

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

The description discloses substantial behavioral detail beyond annotations: it drops a community .tox, loads assets, optionally binds cameras, exposes a renderTOP, returns specific paths/artifacts, and warns about OOM crashes with no friendly error. It also clarifies unsupported platforms and the friendly error behavior, which is highly valuable.

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 dense and well-structured, covering creation, asset sources, camera integration, requirements, VRAM guidance, and return values. It is lengthy but every sentence carries operational weight; nothing is fluff. The front-loading of the core action is effective.

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 (7 parameters, no output schema), the description covers the full lifecycle: what it creates, what it requires, what it returns, and failure modes (OOM, unsupported platforms). The explicit return list partially compensates for the missing output schema and leaves no major gaps.

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 100%, but the description adds meaning by linking parameters to real-world domains: asset sources (Polycam, Postshot, Luma, Nerfstudio), VRAM/resolution tradeoffs for output_res, and how camera_path integrates with create_camera_orbit rigs. This goes beyond the schema's field descriptions.

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 specific verbs ("Drops", "loads", "binds", "exposes") and names precise resources (TDGS .tox, baseCOMP, .ply/.splat asset, cameraCOMP, renderTOP). It clearly distinguishes this tool from generic container or 3D scene creators by focusing on Gaussian splat scenes.

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 for when to use this tool (creating Gaussian splat scenes from specific asset sources) and includes hard requirements (Windows, NVIDIA, TouchDesigner version). It does not explicitly state when not to use alternatives, but the niche nature of the tool makes the intended use obvious.

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