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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real value by listing the returned quantities (there is no output schema) and flagging that the structural form is only a 'guess'. It does not disclose failure behavior, e.g. what happens when no deck can be found or how ambiguity between candidates is resolved.

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?

A single dense sentence, front-loaded with the verb and the 'finds the deck' core, followed by a compact colon-list of outputs. Nothing is padding, though the output enumeration runs long and could be tightened.

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 usefully enumerates what comes back, and annotations cover the read-only profile. Gaps remain for a measurement tool: units/conventions for b, d, L and soffit height are unstated, and no-deck-found behavior is not described.

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 0%, so the description must compensate, and it does partially: 'measures the elements / group given' assigns a role to each of the two parameters. However it leaves precedence undefined (what happens if both group and elementIds are supplied), does not explain what a 'group' string refers to, and does not say both are optional.

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 and resource ('Reads the open model ... finds the deck') and enumerates the exact quantities it reports (b, d, L, soffit height, span axis, deck type, structural form). It is clearly a read/measure step in the ec_wind_* family, distinguishable from ec_wind_apply and ec_wind_remove, though it does not name those siblings explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the survey step before ec_wind_apply, and the parenthetical hints that passing a group or elementIds switches to measuring those instead of auto-finding the deck. There is no explicit when-to-use/when-not statement or guidance on choosing between the two modes.

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