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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the exact calculation formula and default assumptions (modular brick, ⅜ in joint), which is useful behavioral context; it does not, however, describe output formatting or rounding.

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?

Three sentences, front-loaded with the purpose and defaults, then the formula. No filler; every sentence contributes to correct invocation.

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 read-only calculator with seven optional parameters and no output schema, the description supplies the formula, defaults, and scope needed to call it correctly. It is slightly incomplete because it omits an explicit return-value description and usage guidance relative to sibling calculators.

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 all seven parameters are documented in the schema, setting a baseline of 3. The description goes beyond that by showing how the parameters combine in the formula and by stating default brick dimensions, adding relational meaning.

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 exactly what is computed (bricks for a single-wythe wall) and the key inputs (area, brick face size, mortar joint), so the resource is clear. It does not name or explicitly contrast with sibling masonry calculators such as calc_concrete_block, so it falls short of full sibling differentiation.

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?

Gives no when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer from the tool name and sibling list that this is for brick walls rather than concrete block or other wall calculators.

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