setup_cloth_sim

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it 'set up' cloth simulation, which implies mutation, but does not disclose whether existing physics settings are replaced, whether a mesh is required, how baking is affected, or what side effects occur. The 'Template:' prefix adds no behavioral value.

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 short sentence and is mostly front-loaded, but the leading 'Template:' is extraneous filler that does not help an agent. The core action is stated efficiently, but the unnecessary prefix prevents a higher score.

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, a minimal schema, and a one-line description, the tool is under-specified for a physics setup operation. It omits prerequisites, effects on existing physics, return behavior, and how it relates to baking or other physics setup tools. An agent would need to guess or inspect external docs to use it correctly.

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 partially does by identifying 'object' as the target of the simulation and 'pin_group' as an optional pinning vertex group. However, it does not clarify format expectations, whether the vertex group must already exist, or how pinning affects the simulation.

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 clearly states the action and resource: 'Set up cloth simulation with optional pinning vertex group.' This distinguishes it from physics siblings like setup_softbody and setup_rigid_body_world by the cloth-specific resource, though it does not explicitly name those alternatives.

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 this tool versus setup_softbody, setup_rigid_body_world, or add_physics. It does not mention prerequisites such as requiring a mesh or existing vertex groups, nor does it explain when the pin_group should be supplied. Usage is only implied by the tool name and the phrase 'set up cloth simulation.'

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