fem_set_material

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

With no annotations, the description must carry the full behavioral burden. It usefully discloses the minimum material dict keys and that extra keys pass through to the FEM material card, but it does not state whether binding overwrites an existing material, what permissions are needed, or what side effects occur.

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 short, front-loaded with the core action, and then gives only the material example and passthrough rule. Every sentence earns its place and there is no filler.

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 mutation tool with no annotations and a nested object parameter, the description covers the critical material payload but omits prerequisite context about analysis and body references, overwrite behavior, and optional naming. It is adequate to attempt a call with the example dict, but not 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 description coverage is 0%, so the description has to compensate for all four parameters. It adds strong meaning for the complex material object by giving required keys and units, but it says nothing about body, analysis, or name, leaving the majority of parameters undocumented in both schema and description.

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 gives a specific verb and resource: 'Bind a material to a body in an analysis.' That clearly separates it from general material lookup or solver setup tools. It does not explicitly name or compare itself to the closest sibling, fem_set_nonlinear_material, so it stops short of a 5.

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?

There is no when-to-use guidance, no prerequisites, and no alternatives named. The action is implied by the verb, but an agent gets no explicit instruction about when this tool is the right choice versus material_select, fem_set_nonlinear_material, or fem_add_constraint.

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