setup_flip_sim

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says the tool 'sets up' a simulation, but does not explain what this entails—whether it creates a DOP network, modifies the source geometry, overwrites existing setups, or has any side effects. The lack of detail leaves the agent guessing about the operation's scope and mutability.

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 a single, tightly worded sentence that immediately conveys the tool's purpose. Every word contributes meaning, and there is no redundancy or filler. This is appropriately concise.

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?

The tool has 3 parameters, no annotations, and no output schema, so the description must provide sufficient context. It fails to explain what the setup process does, what inputs are required beyond a vague 'source geometry', what the expected output is, or how it interacts with existing scene content. This is inadequate for an agent to invoke the tool confidently.

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. However, it only mentions 'source geometry' which roughly maps to source_path, but adds no meaning beyond the schema's 'Source Path' property. It does not explain the 'name' or 'parent_path' parameters, nor does it clarify what form 'source geometry' should take (e.g., a SOP path, an object path).

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 explicitly states the tool 'Set up a FLIP fluid simulation from a source geometry.' It uses a specific verb ('setup') and names the resource type (FLIP fluid simulation), clearly distinguishing it from sibling 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?

No usage guidance is provided. The description does not say when to use this tool vs alternatives, nor does it mention any prerequisites or exclusions. It simply states what it does without context.

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