simulation_reset

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

With no annotations, the description carries the full burden. It indicates a state-changing operation ('Reset') and clarifies the targeted state, but does not disclose side effects, reversibility, or impact on other garment data (e.g., whether modifications are lost). This is a minimal disclosure for a mutation tool without annotations.

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 waste. It states the action and a clarifying parenthesis, earning its place entirely.

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 simplicity (no parameters, no output schema, no annotations), the description is largely complete. It does not mention return values, but for a reset operation this is not critical. The only minor gap is the lack of explicit linkage to related arrangement-setting tools.

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 tool has zero parameters, so the schema is trivial and the baseline is 4. The description does not need to explain parameter details; it correctly focuses on the action itself. No additional parameter semantics are required.

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 verb 'Reset' and the resource 'garment' to 'arrangement positions', and the parenthetical 'undo the simulation drape' distinguishes it from simulation-related tools. However, it does not explicitly link to a specific sibling like arrange_points or pattern_set_arrangement, leaving slight ambiguity about which arrangement is meant.

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 parenthetical 'undo the simulation drape' implies it should be used after performing a simulation, providing context. But there is no explicit guidance on when not to use it or how it differs from reset-like siblings such as checkpoint_restore, so usage is only implied rather than clearly prescribed.

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