simulation.soft_body

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

Annotations are all false hints (not read-only, not idempotent, not open-world, not destructive), and the description adds only 'Risk: standard; maturity: L3', which is process metadata rather than operational behavior. It does not disclose side effects of a soft-body bake such as geometry deformation over frames, cache creation, or invalidation. No contradiction with annotations, but nearly no behavioral context is added.

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 achieves that by omission, not compression; the 'PartMe Blender Harness command' prefix is boilerplate that restates the title. The two sentences deliver zero operational information, making this under-specification rather than genuine 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?

For a 9-parameter simulation tool with a frame range, an objectId pattern, and a modifierName, combined with an output schema, the description conveys nothing about valid invocation or what result to expect. Sibling differentiation is impossible given six other simulation tools and roughly 140 siblings, so completeness is effectively absent.

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 only 33%, yet the description mentions none of the nine parameters. Five-plus parameters (name, frameEnd, objectId, frameStart, modifierName, _expectedSceneRevision) are undocumented in the schema and completely unexplained by the description, so the description does nothing to compensate for the coverage gap.

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 only restates the command identifier ('PartMe Blender Harness command `simulation.soft_body`') and adds governance metadata about risk and maturity; it never states a verb, resource, or effect. This is a tautology of the tool's name/title, so an agent cannot learn what the operation actually does.

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 when-to-use guidance is provided. The description never mentions alternatives such as blender_simulation_cloth, blender_simulation_rigid_body, or blender_simulation_collision, nor any selection conditions among the many simulation siblings. The only directive, that per-request checks still apply, is a governance reminder, not usage guidance.

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