create_plastic_material

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

No annotations are present, so the description carries the full burden of behavioral disclosure, but it only restates the creation operation and material type. It does not disclose side effects on the model, whether a model must already exist, or how unspecified parameters such as plastic_strain are handled.

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; the core purpose is immediately clear. It is concise to the point of under-specification for an 8-parameter tool, but the structure itself is efficient.

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 8 parameters, 0% schema coverage, and no annotations, a one-sentence description is not enough for correct invocation. The output schema reduces the need to explain return values, but the definition still lacks parameter semantics, usage boundaries, and behavioral side-effect 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%, and the description names none of the 8 parameters. It does not explain how youngs_modulus, yield_stress, plastic_strain, density, model_name, or timeout relate to the elasto-plastic formulation, leaving semantics to be inferred solely from parameter names.

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 specific verb and resource: create an elasto-plastic material with isotropic hardening. This distinguishes the tool from siblings like create_elastic_material, create_hyperelastic_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?

The description implies when to use the tool—when an elasto-plastic material with isotropic hardening is needed—but it does not explicitly state when not to use it or mention alternatives. The differentiation from other material-creation tools is left to inference from sibling names.

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