calculate_beam_load

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

No annotations are provided, so the description carries the burden. It does not explicitly state that the tool is read-only or disclose any side effects. However, the calculation nature implies idempotency, and the return structure is described. Behavior is mostly clear but could be more explicit about safety.

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 two sentences long. The first sentence states the purpose, and the second directs to related bundle tools. No unnecessary words, and key information is front-loaded.

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?

Given the large number of sibling calculators, the description provides a link to bundles for related tools. Input schema is fully described, and output format is listed. This is sufficient for an agent to use the tool correctly.

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 100%, so the schema itself documents parameters well. The description adds value by describing the return format (load_kN_per_m, max_moment_kNm, etc.), which is not in the input schema. This helps agents understand what the tool outputs.

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 states 'Calculate max bending moment and shear for a beam under uniform distributed load,' which is a specific verb+resource combination. It clearly distinguishes from sibling calculators by naming the beam types and return values.

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 does not give explicit when-to-use vs when-not-to-use instructions, but it points to list_bundles for related construction calculators, implying the tool is part of a set. It provides clear context for usage.

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