rsap_add_bar_point_load

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

With no annotations, the description carries the burden, and it does explain key behaviors: 'relative' and 'local' flags, and position interpretation. However, it omits other behavioral traits like whether the load is additive over multiple calls, whether the load case must already exist, or what happens on error.

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 efficiently front-loaded with a one-sentence purpose, then a compact labeled argument list. No wasted words; the arg list is scannable and directly maps to the schema properties.

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 complex 11-parameter tool with no output schema and no annotations, the description covers all parameters, units, and mode flags. It could add more about prerequisites (e.g., existing load case) and selection syntax, but it is sufficiently complete for an experienced structural analysis user.

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?

The description adds substantial meaning beyond the bare schema: it gives units (N for forces, N·m for moments), explains the 'presence' of position as relative fraction or metres, and clarifies the effect of 'relative' and 'local' flags. The schema itself has no property descriptions (coverage 0%), so this is a strong contribution.

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 opens with a specific verb+resource statement: 'Add a concentrated (point) force/moment on bars.' This clearly distinguishes it from siblings like rsap_add_bar_uniform_load and rsap_add_nodal_force by identifying the load type and target element.

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 explicit guidance on when to choose this tool over alternatives. The description only explains parameters, not the context in which a point load vs. uniform load or nodal force is appropriate. Given the sibling tools, an explicit distinction would be helpful.

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