create_line_load

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the load type and target surface, but it does not disclose units, coordinate-system conventions, the need for an existing edge set or step, overwrite behavior, or error conditions. This is thin for a mutating creation operation.

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 a single efficient sentence with the core concept front-loaded and the clarifying definition in parentheses. There is no filler or redundancy, though the brevity comes at the cost of missing necessary operational detail.

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 with 7 parameters, no annotations, and no schema descriptions, the description is too sparse. It omits required preconditions (existing edge set and step), direction semantics, unit conventions, and how it differs from sibling load tools. The presence of an output schema covers return values but not these usage requirements.

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 schema description coverage at 0%, the description must compensate by explaining parameters, but it only hints that 'region_name' refers to an edge set and that 'magnitude' is force per unit length. It says nothing about direction, step_name, model_name, timeout, or name semantics, leaving most of the 7 parameters underspecified.

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 uses a specific verb ('Create') and identifies both the resource ('line load') and the target ('edge set'), adding the clarifying parenthetical 'force per unit length.' It is clear and self-contained, though it does not explicitly compare against sibling tools such as create_shell_edge_load.

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 no guidance on when to choose this tool over related load-creation tools like create_pressure_load, create_body_force, or create_shell_edge_load. No prerequisites, exclusions, or alternative routes are mentioned, leaving the selection entirely to inference.

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