Assign Fluent Material

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

Annotations indicate readOnlyHint=false and destructiveHint=false, so the description must clarify side effects, but it does not. It simply restates the action without disclosing that existing material assignments will be overwritten, or whether zone and material must reference pre-defined objects. No additional behavioral context beyond the annotations is provided.

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?

A single straightforward sentence, 'Assign a material to a Fluent cell zone,' is front-loaded and free of waste. Every word contributes meaning, and the structure is easily parsed.

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 is simple with only two string parameters, so a short description may suffice, but it still lacks essential context such as what the output will be, whether the zone must have a specific type, or any side effects. Since an output schema exists, the description need not explain return values, but behavioral and prerequisite details are missing, making it only minimally complete.

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 coverage is 0% with no descriptions for zone or material. The brief description loosely implies that zone is the target cell zone and material is what to assign, but it does not explain acceptable formats, type expectations, or valid sources (e.g., material names from the Fluent database). It compensates minimally for the missing schema documentation but leaves key semantics unclear.

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 'Assign' with a clear resource 'material to a Fluent cell zone', which precisely identifies the tool's function. It also distinguishes itself from siblings like fluent_set_boundary and fluent_set_solver by specifying Fluent cell zone context. This is a clear and unambiguous purpose statement.

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 when to use the tool (whenever a material needs to be assigned to a Fluent cell zone) but provides no explicit guidance on prerequisites, when not to use it, or alternatives. For instance, it does not mention that the zone must exist or that mechanical_set_material is for Mechanical. The usage context is implied rather than explicitly stated.

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