calculate_cone

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

No annotations provided, so description carries burden. It describes inputs, outputs, and formula but does not disclose potential limits, authorization needs, or side effects. However, for a pure math function, this is adequate.

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?

Description is two sentences, front-loaded with purpose and formula, then usage and output, plus a pointer to related tools. No unnecessary words.

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 mathematical tool with two parameters, the description provides sufficient context: formula, usage scenario, and output. An output schema exists, so detailed return values are not needed in description.

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 with descriptions for radius and height. The description adds value by providing the formula and contextualizing parameters as base radius and height, enhancing understanding beyond schema.

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 computes cone volume and surface areas using the formula V=(1/3)πr²h, and specifies use for geometry or container design. It distinguishes itself from sibling geometry calculators like calculate_cylinder and calculate_sphere by naming the cone.

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?

Description suggests use for geometry or container design and references list_bundles for related math calculators. While it hints at alternatives, it does not explicitly state when not to use this tool versus other geometry calculators.

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