create_hyperelastic_material

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states the creation action and material type. It does not mention side effects, model prerequisites, whether an existing material with the same name is overwritten, or whether an active Abaqus/model context is required.

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 front-loaded sentence with no filler; every word contributes to identifying the tool's purpose. It is concise but arguably too terse relative to the seven-parameter schema, which prevents a higher score.

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 creation tool with seven parameters, no annotations, and no parameter descriptions, this description is insufficient for correct invocation. It identifies the material family but omits required-input semantics, defaults' implications, prerequisites, and behavioral context; the presence of an output schema does not compensate for these gaps.

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 only introduces the 'Mooney-Rivlin' model label, which hints that c10, c01, and d1 are constitutive coefficients without explicitly explaining them. The remaining parameters such as density, timeout, and model_name receive no semantic clarification at all.

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-resource pair ('Create ... material') and names the constitutive model 'hyperelastic (Mooney-Rivlin)', which makes the tool's purpose unambiguous. It is clearly distinguishable from sibling tools such as create_elastic_material, create_plastic_material, and create_viscoelastic_material.

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 about when to choose this tool over alternatives like create_elastic_material or create_viscoelastic_material. The agent must infer selection from the name alone; there are no prerequisites, exclusions, or alternative recommendations.

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