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

With no annotations, the description carries the transparency burden and does well: it discloses that weights are published nominal values, that unmatched designations are listed rather than guessed, and that the output is for estimating/orientation only. This gives users a clear behavioral model beyond the schema.

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, front-loaded with the primary action and contains no filler. Every phrase contributes value: inputs, limit, outputs, matching behavior, and use-case caveat.

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 moderate complexity of a nested array input and no output schema, the description adequately covers what the tool returns (weight per line, totals, counts) and edge behavior (unmatched designations). It lacks explicit error-handling details but is otherwise complete for an estimating tool.

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 input schema already documents the single 'members' parameter and its nested fields (designation, length_ft, qty) with examples. The description adds useful context like 'up to 500 lines' (already in schema as maxItems) and clarifies units (feet, pounds, tons), but does not materially extend the parameter documentation since coverage is 100%.

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 ('Roll') and identifies the resource ('member list') and output ('bill-of-steel ledger'), clearly distinguishing it from sibling tools that compute individual weights or plate/section weights. It also specifies the key inputs (AISC designation, length, piece count) and outputs (weight per line, totals, counts).

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 provides clear context for when to use the tool: for batch member-list takeoffs to produce a ledger, not for design calculations. It also states limitations ('net weight only', 'unmatched designations are listed, not guessed'), which helps guide appropriate use. It does not explicitly name alternative sibling tools, but the batch vs. single-item distinction is implied.

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