setup_rbd_sim

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

The description is extremely terse and does not disclose what setting up an RBD simulation entails—whether it creates DOP nodes, modifies the scene, or has other side effects. With no annotations, the description carries full responsibility for behavioral transparency and fails to provide any such details.

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 free of fluff, but is perhaps too brief. It is a single sentence that, while easy to read, sacrifices necessary detail for brevity, making it less useful than a more balanced description.

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 likely complexity as a simulation setup and the absence of annotations and an output schema, the description is far from complete. It fails to cover prerequisites, configuration options, expected outcomes, or how the simulation is initialized, making it inadequate for an agent to use confidently.

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 has 0% parameter description coverage, and the description only vaguely references 'source geometry', which maps to the required source_path. It does not explain the 'name' or 'parent_path' parameters, leaving essential parameter semantics undescribed.

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 'Set up' with resource 'RBD simulation', clearly identifying the tool's function. It distinguishes the tool from sibling setup tools like setup_pyro_sim, setup_flip_sim, and setup_vellum_sim by explicitly naming the physics type.

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?

No guidance is provided about when to use this tool versus alternatives. The description does not mention contexts, prerequisites, or why an RBD simulation would be chosen over other simulation types.

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