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

No annotations are provided, so the description must disclose behavior. It only mentions 'Returns: {original}', which is vague and does not explain the conversion process, limitations, or whether the tool is read-only. The agent gains little insight beyond the parameter 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 very short (two sentences) and front-loaded with the purpose. It is concise but lacks structure, though every sentence is informative. Could be slightly more detailed without sacrificing conciseness.

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?

Despite an output schema, the description only says 'Returns: {original}', which is unclear and insufficient. It does not explain that the tool requires garment type and sex, which are required parameters. The description leaves significant gaps for effective tool usage.

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% with each parameter described adequately. The description adds no additional meaning beyond the schema, such as constraints or relationships between parameters. Baseline score of 3 is appropriate.

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 clearly states the tool converts clothing sizes between EU, US, and UK systems, using a specific verb and resource. It distinguishes from sibling tools like convert_shoe_size and calculate_bra_size_convert by specifying 'clothing size'.

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 advises to 'See list_bundles for related conversions calculators' but provides no explicit guidance on when to use this tool versus alternatives like convert_shoe_size or calculate_bra_size_convert. It also lacks when-not-to-use conditions.

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