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

Annotations already cover readOnlyHint and openWorldHint=false, and the description adds real behavioral content: it declares the exact row sources, the refusal condition, the four possible statuses (PASS / FAIL / BLOCKED / OUTSIDE RANGE OF VALIDITY), and that many rows make it run long as a website job. It doesn't cover output shape in detail, but that is largely a schema matter here.

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 core purpose, the force-row source, and the NOT CONCURRENT caveat are front-loaded in the first sentence; the trailing 'Read-only' and 'Takes a while' sentences earn their place. The first sentence is dense with parentheticals, but for a 23-parameter tool it is not wasteful.

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 23-parameter assessment tool with no output schema, the description covers what is assessed, where force rows come from, refusal behavior, and the status vocabulary returned. It omits any explanation of the utilisation values returned and the effect of some flags (e.g., secondaryActions), leaving minor gaps.

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 description coverage is 91% and the nested definitions are unusually thorough (links, rebar rows, stations). The description adds a little framing for cases and stations but mostly defers to the schema, so it does not need to carry parameter meaning itself.

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?

It states a specific verb and resource ('CS 455 ULS assessment of reinforced concrete beam sections') and names the checks performed (N–M flexure, shear, torsion cl 5.17–5.27) with per-row status output, which clearly separates it from siblings like cs455_describe_section or slab_assess.

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?

It gives a clear operating context (reads concurrent force rows at chosen element ends for chosen combinations) and an explicit exclusion: a moving-load case from a model analysed without 'Normal + Concurrent Force' is refused as NOT CONCURRENT. It stops short of naming sibling alternatives such as cs455_describe_section or cs455_export_calc_sheet for those tasks.

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