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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description usefully adds that the tool requires no model and enumerates the computed quantities, which is behavior an agent cannot infer from the annotations alone; error handling and input validation behavior remain unstated.

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 dense sentence, front-loaded with the transformation 'Bar arrangement → ...'. It packs many output items but remains fairly tight, though domain shorthand like 'Annex LL steel forces' may require prior knowledge.

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?

With no output schema, the description does well to enumerate the returned quantities, but the input side is complex (nested top/bottom layers, 8 parameters, 50% schema coverage) and the description provides no guidance on the undocumented gamma and alpha parameters. It is adequate but incomplete for an agent to call this correctly without carefully inspecting the schema.

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 only 50%, with gamma_c, gamma_s, alpha_cc, and thickness_mm undocumented in the schema. The description adds no parameter-level meaning, such as defaults for partial factors or how top/bottom layers and cover interact, so it fails to compensate for the coverage gap.

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 computation: deriving RC slab/shell capacities from a bar arrangement, including per-layer area, effective depth, lever arms, moment and force capacities. It is clearly a calculation tool, but it does not explicitly differentiate itself from assessment siblings such as slab_assess or cs455_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?

The phrase 'Needs no model' implies it should be used for standalone capacity calculation from bars, and the link to 'RC Slab & Shell Assessment routes' gives context. However, there is no explicit when-not guidance or named alternative for cases where a model-based assessment is preferred.

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