setup_rbd_sim

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses very little. It does not say whether nodes are created fresh or merged into an existing network, what happens on repeated calls, whether the operation is destructive, or what state the tool leaves behind. "with fracture and solver" is the only structural hint offered.

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?

A single front-loaded sentence with no filler or redundancy. Its brevity is efficient structuring, though it edges toward under-specification for a four-parameter mutation tool.

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, no output schema, and zero parameter documentation, the definition omits nearly everything an agent needs: side effects, node creation semantics, parameter meaning, and any indication of the result. For a tool that mutates a DCC scene graph, the description is far too thin.

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 0% across four parameters, so the description must compensate and largely does not. "Fracture" loosely gestures at pieces_type and "network" at name/geo_path, but ground and the default voronoi choice are entirely unexplained, as is the expected format of geo_path.

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 concrete verb ("Build") plus a specific resource ("RBD rigid-body simulation network") and names the components it installs ("fracture and solver"). That implicitly separates it from the sibling setup_flip_sim / setup_pyro_sim / setup_vellum_sim tools, though it never explicitly states the contrast.

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 statement of when to choose this over the other simulation-setup siblings, nor any prerequisite or precondition (e.g. whether a geometry node must already exist at geo_path). The agent is left to infer usage entirely from the tool name.

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