create_viscoelastic_material

Does 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 states only that a material is created — nothing about side effects (e.g., overwriting an existing material of the same name), validation of Prony series weights, or whether the operation is reversible. For a creation tool with zero annotation coverage, this is a significant omission.

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 compact and front-loaded with the purpose statement, followed by a single Args entry. There is no filler, repetition, or wasted words. The docstring-style Args block is slightly awkward in a tool description since the input schema already encodes the parameter shape.

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 7-parameter creation tool with no annotations and no schema-level parameter descriptions, the description is far from complete: no prerequisites, no validation constraints (e.g., bounds or sums on g_i/k_i), and no side-effect disclosure. The presence of an output schema mitigates the need to document return values, but it does not compensate for the missing operational 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 must compensate, but it documents only relaxation_data as 'list of (g_i, k_i, tau_i) Prony series terms'. While that is the most opaque parameter, the tuple labels are never defined (g_i = relative shear modulus, k_i = relative bulk modulus, tau_i = relaxation time), and the other six parameters receive no semantic explanation 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 opens with 'Create a viscoelastic material with Prony series' — a specific verb, resource, and constitutive formulation. The resource type inherently distinguishes it from sibling material tools like create_elastic_material, create_plastic_material, and create_hyperelastic_material, though it never names them explicitly.

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 on when to choose this tool over the many sibling material-creation tools, and no prerequisites or exclusions are stated (e.g., whether an active model/part must exist first). With a sibling list this dense, the absence of routing guidance is a real gap; usage intent is only implied by the material-type name.

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