mdpa_set_entity_properties

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

With no annotations, the description carries the full burden. It does disclose a meaningful behavioral constraint (new type must match node count), but it is silent on whether the edit is applied in place, how the 'overwrite'/'output' flags change behavior, and what the mutation destroys. The node-count rule is useful added context, but the mutation/overwrite semantics are left opaque.

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-loaded with the core action ('Change the property id... and/or the Kratos type name') followed by the constraints and selection method. Dense but efficient, with no filler sentences.

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 described, and the description covers the core operation well. However, for an 8-parameter mutation tool with no annotations, the silent path/output/overwrite parameters and the unspecified write/overwrite behavior leave the agent under-informed.

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 carries the whole load. It meaningfully explains property_id, new_type, kind, ids, and sub_model_part (including that property_id maps to a Materials.json entry), but path, output, and overwrite are undocumented in both description and schema, leaving gaps it does not compensate for.

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: change the property id (Materials.json mapping) and/or the Kratos type name of elements/conditions. This is concrete and far from tautological. It does not, however, name or distinguish itself from near-siblings like mdpa_set_properties or mdpa_set_elemental_data, so an agent must infer the boundary.

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?

It gives real operational guidance – kind must be 'element'/'condition', the new type must have the same node count, and entities are selected by ids or sub_model_part membership. But it offers no explicit when-to-use versus the sibling tools that also set properties/materials, so selection remains inferred.

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