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

No annotations present, so description must cover behavior. It mentions inputs both circumference and diameter, but the schema only includes circumference_mm, creating a discrepancy. It states returns all systems, but from_system parameter suggests system-specific output. No disclosure of side effects, permissions, or edge cases.

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 and a reference to list_bundles. Efficient, but could be slightly more structured without losing clarity.

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 existence of an output schema (not shown), description lacks detail on return format and fails to address the inconsistency between stated diameter input and actual schema. No safety info or annotations provided, leaving gaps for agent.

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 0%, so description must explain parameters. It mentions inputs (circumference mm or diameter mm) but does not match schema (no diameter parameter). Does not explain the from_system enum or how to use 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?

Description clearly states the tool finds ring sizes using finger circumference or diameter, and lists supported sizing systems. However, it does not explicitly distinguish from the sibling tool 'calculate_ring_size_convert', which likely performs conversion between systems.

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?

Provides a usage context ('Use for jewelry shopping') and references list_bundles for related calculators, but lacks guidance on when to use this tool versus alternatives, and does not mention 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.