setup_fluid_domain

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

No annotations are provided, so the description carries the full burden. It states the action but does not disclose side effects, whether it creates or replaces a domain, whether an existing object is required, or what 'Template:' means. This is a significant gap for a mutation/setup tool.

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 sentence and front-loads the core action. The 'Template:' prefix is unnecessary and slightly confusing, but the overall length is appropriate.

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 parameter documentation, the description leaves key questions unanswered: what domain should reference, what emitter does, and what the setup entails. The output schema helps with return values but not with invocation semantics.

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%, and the description only restates the parameter names ('domain', 'optional emitter') without explaining accepted values, formats, or behavior. The optionality of emitter is already encoded in the schema's default null, so no new meaning is added.

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 ('Set up') and resource ('fluid simulation'), and names the two inputs (domain, optional emitter). This clearly distinguishes it from sibling physics tools like setup_cloth_sim and setup_softbody, even without explicitly naming alternatives.

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 description implies the tool is for creating fluid simulations, but it gives no explicit when-to-use guidance, prerequisites, or exclusions relative to add_physics or other setup_* siblings. An agent must infer usage from the name and resource.

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