mdpa_set_sub_model_part_data

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

With no annotations, the description carries the full burden. It does add real behavioral context: None leaves a reference unchanged, and table ids 'must exist as top-level Tables' (a validation constraint). But it never mentions the overwrite flag, whether the file is written in place, or what happens to existing data not named.

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?

A single dense sentence with the verb and replacement semantics front-loaded, then the parameter mapping. No filler, though the run-on construction with parentheticals makes it slightly harder to scan than it needs to be.

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 on a file with zero annotations, four of seven parameters undocumented, and an unexplained overwrite=false default that sits awkwardly against the word 'wholesale,' the description is incomplete. The existing output schema means return values need not be described, but the write/overwrite semantics are a real gap.

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 schema provides no parameter help. The description compensates for three of seven parameters (data, tables, properties) with genuine MDPA-block semantics and a validity constraint on tables, but leaves path, name, output, and overwrite completely undocumented.

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 and resource: 'Replace a SubModelPart's data references wholesale,' and enumerates the three MDPA blocks affected (data, tables, properties). An agent can tell this targets SubModelPart data references, but nothing distinguishes it from the close siblings mdpa_edit_sub_model_part, mdpa_set_properties, or mdpa_set_table.

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 when-to-use guidance, no prerequisites, and no routing to alternatives. The word 'wholesale' implies a replace-all semantic rather than a merge, but the description never says when this is preferable to mdpa_edit_sub_model_part or mdpa_create_sub_model_part.

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