Approximate face up size for a shape and carat weight

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

No annotations provided, so description carries full burden. It explains the scaling method (cube root), supported shapes, and explicitly states the output is approximate and not a guarantee, which is good behavioral disclosure.

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?

Three sentences, each essential: primary function, supported shapes and method, and a necessary caveat. No redundant information, well-paced for quick scanning.

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 tool with 2 parameters and no output schema, the description is complete: it explains what it returns, how it computes, and its limitations. Slightly lacking explicit mention of units, but 'millimeter dimensions' is clear.

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%, so baseline is 3. The description adds value by explaining the scaling method, supported shapes, and units (mm implied), going beyond the schema's property descriptions.

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 it provides approximate face up millimeter dimensions for a diamond given shape and carat weight. It lists supported shapes and distinguishes itself from unrelated sibling tools about other diamond topics.

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 clearly indicates when to use the tool: for approximate dimensions. It does not explicitly exclude scenarios or mention alternatives, but the context is clear and the caveat about typical proportions provides usage guidance.

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