mdpa_set_nodal_data

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose meaningful traits: float vs string value handling, that string vectors are kept verbatim, and that fixed=true constrains the rows. But it omits the overwrite behavior, what 'path' refers to, and the response/output behavior for a mutation tool.

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 write action and the target resource, kept to a compact multi-clause sentence with no filler. The nested parentheticals are mildly dense but each clause carries information.

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. But for an 8-parameter mutation tool with zero annotations and 0% schema coverage, leaving path, variable, overwrite, and output unexplained is a real gap; the description is only partially complete for correct invocation.

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 for all 8 parameters. It usefully explains value (scalar vs verbatim vector), fixed (constrained rows), and the node_ids/selector selection path, but leaves path, variable, overwrite, and output undocumented in either the schema or the description.

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 (write) and resource ('Begin NodalData <variable>' block value as an initial condition on mesh nodes), which distinctively separates it from siblings like mdpa_set_elemental_data and session_set_nodal_values. The example (TEMPERATURE) grounds the purpose concretely. It does not explicitly name a sibling, so it stops short of a 5.

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 usage by explaining it writes initial conditions to chosen nodes and how to select them (node_ids or selector), so an agent can infer when to reach for it. However, it never states when to use this over mdpa_set_elemental_data or session_set_nodal_values, and gives no prerequisites or exclusions.

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