blender_physics_fluid_quick

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

No annotations exist, so the description carries the full burden of behavioral disclosure. It reveals that a Mantaflow liquid or gas simulation is created, but it does not disclose side effects such as whether existing physics settings on the domain or flow objects are overwritten, whether a bake is triggered, or what scene changes the agent should expect.

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 two short sentences with no filler. It front-loads the primary action and required objects, then adds the Mantaflow and liquid/gas details. Every sentence earns its place.

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 physics setup tool with no annotations and no output schema, the description is somewhat thin. It explains what is created but not whether simulation baking is included, whether existing fluid settings are replaced, or what the agent should do after calling this tool. The naming and sibling context help, but important operational context is missing.

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 100%, so the schema already documents all five parameters. The description adds no parameter-specific meaning beyond what the schema provides; domain and flow roles are already defined in the input schema. This meets the baseline but does not elevate it.

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 names a specific verb ('Creates') and a precise resource ('fluid simulation setup with a domain and flow object'), and adds a meaningful technology detail ('Mantaflow-based liquid or gas'). It is clearly distinguishable from sibling physics tools like rigid_body_add, cloth_add, and soft_body_add.

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 'Quick' prefix and 'setup with a domain and flow object' imply the intended use, but there is no explicit when-to-use or when-not-to-use guidance, and no alternative fluid tool is named. The guidance is adequate at an implied level, but the agent must infer when this is the right choice versus a more manual or detailed fluid workflow.

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