Add thermal expansion properties to a material in an Abaqus model by specifying expansion coefficient and reference temperature.
Add thermal expansion to an existing material.
| Name | Required | Description | Default |
|---|---|---|---|
| timeout | No | ||
| model_name | No | Model-1 | |
| material_name | Yes | ||
| expansion_coefficient | Yes | ||
| reference_temperature | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.0Does 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 conveys a mutating operation on an existing material but does not address side effects, error behavior if the material is missing, overwriting existing properties, or what changes occur in the model.
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?
One sentence, front-loaded, and free of filler. It is appropriately concise as a purpose statement, even though other dimensions suffer from the lack of elaboration.
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?
With no annotations, 0% parameter coverage, and five parameters including a non-obvious reference_temperature, this is too sparse for reliable invocation. The description acknowledges the existing-material prerequisite but omits units, defaults, and behavioral context.
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 needed to clarify expansion_coefficient units, reference_temperature meaning, and model_name role. It only relates to 'thermal expansion' broadly and leaves most parameter semantics 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?
States a specific action ('Add thermal expansion') and target ('existing material'), clearly distinguishing it from sibling material-property tools like create_thermal_conductivity and create_specific_heat. An agent can tell exactly what this tool does without opening the schema.
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 phrase 'existing material' implies a prerequisite and distinguishes this from material-creation tools, but it does not explicitly state when to use this tool over alternatives or mention exclusions. Usage context is present only implicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.