calculate_shoe_size

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

The description mentions to-system and gender as inputs, which are absent from the schema, and includes Japanese system not in the enum. This misrepresents actual behavior.

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?

Relatively concise at three sentences, but the 'Inputs' line is redundant given the schema, and the misleading info adds unnecessary length.

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 having an output schema and basic info, the description doesn't match the actual schema, leaving the agent with incorrect expectations about inputs and possible conversions.

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?

Adds meaning beyond schema (to-system, gender) but inaccurately, as those parameters don't exist. The schema covers existing params adequately, but description is misleading.

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 sizes and lists the systems (EU, US, UK, Japanese), but it claims support for Japanese and additional parameters not in the schema, slightly muddying purpose.

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?

Only suggests use for international shopping; no guidance on when to use this versus sibling tools like convert_shoe_size, and no exclusion criteria.

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