materials_set_property

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses that the file is created if missing, how properties_id is auto-assigned, that preset fills the law/defaults then gets overridden, that existing entries are merged, and that replace=true rebuilds from scratch. It does not cover error/permission conditions or id-collision behavior, keeping it short of a 5.

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?

Front-loads the core action and primary key in sentence one, then layers behavioral detail with no filler. The prose is dense and slightly clause-heavy, but every sentence earns its place.

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?

An output schema exists, so return values need not be explained, and the description thoroughly covers the mutation/merge semantics an agent needs. It omits failure modes and validation expectations (e.g., the role of materials_check), which for a write tool with no annotations would have been valuable.

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 coverage is 0%, so the description must compensate and largely does: it explains preset, constitutive_law, variables, tables, replace, properties_id, and model_part_name semantics. It does not describe the internal structure of the free-form variables/tables objects or the materials_file path handling, leaving a gap for a nested-object-heavy signature.

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 verb+resource ('Add or update ONE entry of a Materials.json'), the key field ('keyed by model_part_name'), and explicitly contrasts with the sibling create_materials. An agent can distinguish this incremental upsert from any of the ~90 siblings 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?

Names the alternative and the condition that selects it: 'the incremental counterpart of create_materials, which rewrites the whole file.' It also routes the agent to list_material_presets for the preset argument, giving clear when-to-use context for both major choices.

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