setup_flip_sim

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 behavioral disclosure. It says the tool 'builds' a network, but it does not disclose whether existing nodes are overwritten, whether new nodes are created under the given name, whether cooking is triggered, or any side effects beyond node creation.

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 compact and front-loaded: purpose first, then usage context, then parameter list. Every sentence contributes meaningful information without redundancy.

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 setup tool with no annotations and no output schema, the description gives a reasonable starting point, but it omits important call-time details like allowed domain values, units for particle_sep, whether the function returns a node path, and behavior on naming conflicts.

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 compensate. The Args list adds basic meaning for all four parameters, but 'domain: Domain type' is vague, particle_sep lacks units, and source_geo is not explained beyond 'Source SOP path.' It is helpful but not detailed.

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 first sentence states a specific verb and resource: 'Build a FLIP fluid simulation network from source geometry.' The phrase 'FLIP fluid simulation' clearly distinguishes it from sibling setup tools like setup_pyro_sim, setup_rbd_sim, and setup_vellum_sim.

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?

It explicitly positions this tool as 'Preferred over manual DOP wiring' and explains the value proposition: 'builds the entire FLIP network in one call.' It also hints at sourcing alternatives, though it does not explicitly contrast with sibling setup tools or state when NOT to use it.

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