setup_cloth_sim

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

With no annotations, the description carries full burden but discloses little beyond the basic action. It does not mention side effects, prerequisites, whether existing physics are overwritten, or whether the target object must be a mesh. Only the pinning vertex group is noted.

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. It communicates the primary purpose and a key parameter in minimal words.

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?

For a physics setup tool with no annotations, the description is under-specified. It does not explain when to use it, what happens to existing physics, or prerequisites. The output schema may cover return values, but behavioral and contextual gaps remain.

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%, so the description must compensate. It clarifies the pin_group parameter as 'optional pinning vertex group' but leaves the required 'object' parameter unexplained, making its role ambiguous.

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?

Description clearly states the action 'set up cloth simulation' and distinguishes it from sibling physics setup tools like setup_softbody and setup_rigid_body_world. The mention of an optional pinning vertex group adds specific scope.

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 on when to use cloth simulation versus alternatives such as soft body or rigid body. There are no exclusions, prerequisites, or alternative tool references, leaving usage context solely implied by the purpose.

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