setup_softbody

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 disclosing behavior. 'Set up softbody simulation' is essentially a restatement of the tool name and reveals nothing about what actually happens: whether it modifies the provided object, creates a physics modifier, affects existing settings, or has side effects. This is too vague to inform an agent about the tool's behavior.

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 short but under-specified. The 'Template:' prefix is unnecessary noise, and the remaining sentence merely rephrases the tool name without adding useful operational detail. This is under-specification rather than effective conciseness.

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 a single parameter and an output schema, the tool is simple, but the description still leaves critical gaps: the meaning of the object parameter is undocumented, no behavioral details are provided, and no guidance distinguishes this from similar physics setup tools. The description is not complete enough for reliable tool selection or invocation.

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 a single 'object' parameter with 0% description coverage, and the description does not mention it at all. The agent is not told what 'object' refers to or how it is used in the softbody setup process. The description provides no compensation for the schema's lack of parameter documentation.

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 and resource: 'Set up softbody simulation.' This clearly identifies the tool's purpose and distinguishes it from sibling tools like setup_cloth_sim or setup_rigid_body_world by naming 'softbody.' However, the odd 'Template:' prefix introduces slight ambiguity and no further specifics are provided.

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?

There is no guidance about when to use this tool versus alternatives. The description does not mention prerequisites, when not to use it, or how it differs from related setup tools such as setup_cloth_sim or setup_rigid_body_world. Usage context is only implied by the tool name.

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