calculate_shoe_size_convert

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

No annotations exist, so the description carries full burden. It mentions the output fields but omits details like rounding behavior, handling of non-integer sizes, or whether conversions are exact. The return format is stated but not comprehensively described.

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?

Two sentences: first defines action and target systems, second details output and provides a pointer to related tools. No redundant information; purpose is front-loaded.

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 simple conversion tool with full schema and output indication, the description covers the core. However, it lacks edge-case handling, precision notes, and usage context that would make it fully self-contained.

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 clear parameter descriptions. The description does not add extra meaning beyond the schema; it only states the purpose and output. Baseline score of 3 is appropriate as the schema already handles explanation.

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 shoe size between EU, US (M/W), and UK systems, and specifies the return object with field names. It distinguishes itself from siblings by naming the exact systems and providing output structure.

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 'See list_bundles for related conversions calculators', which hints at alternatives but does not explicitly state when to use this tool vs others like convert_shoe_size or calculate_shoe_size. No prerequisites or exclusion criteria are given.

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