calculate_ring_size_convert

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

The description claims inputs include 'to-system' which is not present in the input schema. This is a direct contradiction with the tool's actual behavior, severely misleading an AI agent. No annotations exist to clarify.

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 but includes inaccurate information ('to-system') and an inconsistent system list, making it inefficient and harmful despite brevity.

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?

Given the tool's moderate complexity (multiple sizing systems) and the existence of an output schema, the description should clarify the conversion direction, but it instead misstates the input structure. It does not fully equip the agent to use the tool correctly.

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?

While the schema describes the two existing parameters, the description adds an incorrect third parameter ('to-system'), introducing confusion rather than adding value. The schema coverage is 100% but the description undermines it.

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 ring sizes between systems and mentions international jewelry shopping. However, the list of systems is inconsistent with the enum (e.g., 'Japan' vs 'JP', missing 'FR'), and the mention of 'to-system' is misleading since it isn't in the schema.

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?

It provides a use case ('international jewelry shopping') and points to related tools via list_bundles, but does not explicitly state when to use this tool versus other conversion tools or when not to use it.

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