calculate_cone

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

No annotations exist. The description covers core behavior (compute and return values) adequately but doesn't add details like side-effect-free nature or error handling. For a computation tool, this is minimally sufficient.

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 two information-dense sentences plus a helpful reference. No fluff; every sentence earns its place.

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?

With an output schema present, the description's mention of 'Returns volume and areas' suffices. For a simple tool with well-documented parameters and output, it is fully complete.

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% with descriptions for radius and height. The description merely repeats 'Inputs: radius, height,' adding no new meaning, so it meets the baseline.

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 specifies the tool computes cone volume and surface areas with formulas, clearly distinguishing it from other calculation tools by naming the geometric shape and outputs. It references bundled math calculators for alternatives.

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 states 'Use for geometry or container design,' providing clear context. It mentions 'See list_bundles for related math calculators' for alternative discovery, but lacks explicit when-not-to-use guidance.

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