add_cloth

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

No annotations are provided, so the description must fully convey behavioral traits. It only states the action (adding cloth simulation) but does not disclose side effects, such as whether the mesh is modified in-place, whether previous cloth simulations are removed, or any permissions or destructive nature. This leaves significant uncertainty.

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?

Description is very concise with two short sentences. No fluff, but could be slightly more structured by separating the parameter explanations. It earns its space.

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 no output schema and low schema coverage, the description should provide more context about the tool's behavior, prerequisites, and possible errors. It lacks information about what happens after adding cloth, any return value, or how to undo the operation. Incomplete for a simulation tool.

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 add meaning. It explains that 'quality' controls simulation accuracy (1-10) and 'mass' is in kg, which adds useful context beyond the schema. However, the 'name' parameter is not explained, and the coverage is incomplete.

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 'Add cloth simulation to a mesh object', which is specific. However, it fails to differentiate from the sibling tool 'physics_add_cloth', which appears to perform a similar function. Without distinction, an AI may be uncertain which tool to use.

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 alternatives. Description does not mention prerequisites, such as whether the mesh object must be selected or if a specific mode is required. There is a sibling 'physics_add_cloth' that likely overlaps, creating ambiguity.

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