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

Annotations already declare this is a read-only, idempotent, non-destructive, closed-world operation, so the description adds little on that front. It provides no additional behavioral context such as handling of unsupported systems or how missing target-system conversions are handled, despite implying inputs that the schema does not contain.

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 short and front-loads the main conversion purpose, but it wastes space on a questionable 'See list_bundles' pointer and on input names that are not actually in the schema. The structure is acceptable but the content is imprecise.

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 two required parameters, full schema coverage, and an output schema, the description should at least accurately reflect the inputs. Instead it references a nonexistent to-system and gender and omits the enum constraints, leaving an agent unsure how the target system is actually specified.

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 the schema already documents size and from_system. However, the description lists 'to-system' and 'gender' as inputs even though neither exists in the schema, and it omits the schema's actual enum values, making the parameter guidance actively misleading rather than additive.

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 names a specific verb and resource (convert shoe size) and lists systems, but it claims to support Japanese systems even though the schema's from_system enum only offers EU, US_M, US_W, and UK. The name also overlaps heavily with sibling tools calculate_shoe_size_convert and convert_shoe_size, and the description does nothing to distinguish this tool from them.

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 only guidance is the vague phrase 'Use for international shopping,' which does not say when to choose this tool over the near-identical calculate_shoe_size_convert or convert_shoe_size siblings. No exclusions, prerequisites, or alternative routing are given.

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