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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not note that results are approximate, that sizing tables differ by garment/sex, or any caveat about conversion accuracy. The cryptic fragment 'Returns: {original}' conveys no real behavioral information and appears to be an unfilled template.

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 first sentence is tight and front-loaded, which is good. But the second sentence is a template artifact ('Returns: {original}') that consumes space without communicating anything, and the list_bundles pointer is low-value for actually invoking this tool.

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?

An output schema exists, so the description need not explain return values. However, given a four-required-param conversion whose correctness hinges on garment type and sex, the description omits the very context that makes the conversion meaningful, and the placeholder return text leaves the entry looking unfinished.

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 100%, with all four required params (sex, size, garment, from_system) documented and three of them enum-constrained, so the baseline is 3. The description contributes nothing further — it never mentions that size interpretation depends on 'garment' and 'sex' — so it does not exceed the baseline.

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 (Convert) and resource (clothing size) with the three systems it spans (EU, US, UK), which distinguishes it from siblings like calculate_shoe_size_convert, calculate_bra_size_convert, and calculate_ring_size_convert. It does not, however, mention that garment and sex affect the result, so the scope is slightly incomplete.

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?

No when-to-use or when-not-to-use guidance and no routing to alternative sibling converters (e.g. shoe/bra/ring size converts). The only pointer is to 'list_bundles', which is a discovery tool rather than a competing calculator, so an agent gets no help choosing between converters.

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