convert_shoe_size

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

No annotations are provided, so the description carries full burden. It merely states 'Returns converted size' without detailing any behavioral traits such as handling of invalid inputs, rounding, or whether gender is needed (despite being mentioned). The mismatch between described and actual parameters undermines transparency.

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 two sentences long, which is concise. The first sentence defines purpose, the second adds a use case, and the third lists inputs/outputs. However, there is slight redundancy (e.g., 'Inputs: ...' is already in schema) and the incorrect mention of gender wastes space. The structure is functional but not excellent.

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 return value explanation is not needed. However, given the complexity of shoe size conversion (gender-specific for US sizes) and the existence of a sibling tool, the description fails to address these nuances. The gender parameter is missing from the schema but mentioned, leaving the agent uncertain. The description is incomplete for effective tool invocation.

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?

Input schema has 100% coverage (all parameters described), so baseline is 3. However, the description lists 'size, from, to, gender' as inputs, but the schema lacks a gender parameter. This inaccuracy reduces the value added by the description. The description does not explain the meaning of the enum values beyond what schema provides.

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 states the tool converts shoe sizes between EU, US, and UK systems, which is clear. However, it mentions a 'gender' parameter not present in the input schema, causing confusion. Also, a sibling tool 'calculate_shoe_size_convert' exists with a similar purpose, but no differentiation is provided, reducing clarity.

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 suggests 'Use for online shopping' as a use case, but provides no guidance on when not to use it or how it differs from the sibling 'calculate_shoe_size_convert'. The pointer to list_bundles is vague and does not help in tool selection.

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