Run Fluent Iterations

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

The description adds no behavior beyond the annotations, which are all false and thus convey little. It does not disclose side effects (e.g., whether iterations overwrite results, whether the solver is blocking, or whether a session must be already initialized). Annotations already declare readOnlyHint=false, but the description provides no additional context.

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, grammatically correct sentence with no wasted words. However, it is so brief that it borders on under-specification rather than effective conciseness, providing minimal information for a tool in a complex workflow.

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?

Given the tool's role in a Fluent simulation workflow, the description omits critical context such as when to run it relative to reading a case, initializing, or solving. It does not mention that it likely requires an existing Fluent session. While an output schema exists, the description fails to cover usage context and integration with sibling tools.

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, but it mentions no parameters. The schema itself includes defaults and ranges for 'iterations' and 'timeout', but the description adds no meaning beyond those structured fields, leaving their semantic roles (e.g., number of iterations, total time limit) unexplained.

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 states a clear verb ('Run') and resource ('Fluent solver iterations'), distinguishing it from siblings that launch Fluent, read cases, or get residuals. It does not explicitly compare with alternatives, but the action is specific enough to differentiate it from most sibling tools.

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 guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites like an active Fluent session or case setup, nor any exclusions. The context is implied only by the tool name and description.

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