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

Annotations already declare readOnlyHint=true, so the 'Read-only' sentence is confirmatory rather than additive. Beyond that, the description discloses meaningful behavior: it reads through the shared section library, uses CIVIL NX published properties for catalogue sections, groups elements by section or thickness, and returns proposed deck type, depths, width-against-depth parts, units, initial temperature, and existing EC1T_ cases. It stops short of describing empty-model or error behavior.

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 front-loaded with the core verb and resource and contains no filler. However, it is one long, heavily nested sentence with parentheticals, which makes the return-content list harder to scan than a short structured list would be.

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?

There is no output schema, so the description must carry return-value information, and it does so extensively: section grouping, proposed deck type, h and D depths, width-against-depth parts per material, units, initial temperature, and EC1T_ cases. Given three optional parameters and minimal annotations, this is largely complete, though precedence between input sources and edge-case behavior remain unstated.

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 67%, with group and useSelection documented in the schema but elementIds left bare. The description adds meaning by explaining that the deck can come from a structure group, an element list, or the CIVIL NX selection, which maps to the three parameters, but it does not clarify precedence among them or add syntax details beyond the schema.

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?

States a specific verb (Reads) and resource (the open model / deck sections for thermal loads) and explains the grouping logic: beams by section, plates by thickness. This clearly distinguishes it from sibling mutation tools like bridge_thermal_apply or bridge_thermal_calc.

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 when to use it by naming the deck sources (structure group, element list, CIVIL NX selection), but it does not explicitly state when to choose this tool over siblings such as bridge_thermal_calc or bridge_thermal_apply. Usage is inferable from the read-only framing, but no exclusions or workflow prerequisites are given.

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