Add loads

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

The description discloses important behavioral details like sign convention (downward negative) and coordinate system options, which go beyond basic annotations. However, it does not mention whether loads replace or accumulate.

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?

Two concise sentences front-load the main purpose and key details, with no wasted words.

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?

The description covers inputs adequately but lacks output schema info and does not specify whether loads are added incrementally or overwrite. Slightly incomplete for a complex tool.

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?

With 0% schema description coverage, the description adds significant meaning: units, sign conventions, and sys enum semantics. However, it does not fully detail all parameters like wx, wy.

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 clearly states the tool adds nodal loads, member UDLs, and self-weight factor, with specific units and sign conventions. It distinguishes well from sibling tools like add_members or add_supports.

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 for load definition but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria. No guidance on prerequisites or sequencing.

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