set_load

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

The '[MODIFIES MODEL]' tag is a weak behavioral indicator, but the description doesn't state whether this overwrites existing components, merges them, or only accepts specific values. It doesn't describe side effects like validation failures or partial modifications. With no annotations provided, the description carries the full burden but fails to explain the behavior beyond 'set components.' This is a significant gap.

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 extremely short, but this is under-specification rather than conciseness. It front-loads the '[MODIFIES MODEL]' modifier, which is useful, but the rest is a single sentence that omits essential information. A well-structured description should provide enough detail without being verbose, and this falls below that threshold.

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 tool that modifies model state, with two parameters including a nested object, and no annotations or output schema explaining return values, the description is woefully incomplete. It doesn't mention what the tool returns (though there is an output schema, the description doesn't add context), nor does it explain how components interact with existing model data. Given the complexity of the action, this is completely inadequate.

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 for missing parameter explanations. It doesn't define what 'components' means: what are the keys and values? Are they material names, load magnitudes, or something else? 'load_name' is fairly self-explanatory, but 'components' is an open-ended object that the description completely fails to clarify. This is a critical deficiency.

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 starts with '[MODIFIES MODEL]' and says 'Set components on one existing named load.' It clearly indicates the action is to modify a load by setting components, and it specifies that the load must already exist. This distinguishes it from other sibling tools like set_material_assignment or create_named_selection. However, 'components' is vague and the description doesn't elaborate on what kinds of components beyond 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?

There is virtually no guidance on when to use this tool versus others. It doesn't mention prerequisites (e.g., the load must exist, should be created first), nor does it contrast with create/delete load tools. No statement on typical usage scenarios or limitations. The only hint is that it modifies an existing load, but it doesn't explain why an agent would need this versus other actions.

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