calculate_cylinder

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

Describes core behavior: computes two formulas, accepts radius and height, returns volume and area. No annotations present, so description carries full burden. Discloses enough for a simple calculation tool.

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 clear, front-loaded sentences. No redundant words. Purpose, use case, inputs, outputs, and reference to related tools all included efficiently.

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 tool simplicity and presence of output schema, description covers purpose, usage, inputs, and outputs. Could mention that surface area includes ends (implied by formula) but not necessary.

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 covers 100% of parameters with descriptions. Description restates inputs (radius, height) but adds no additional constraints or formatting. Baseline 3 is appropriate.

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?

Clearly states it computes cylinder volume and surface area with formulas. Provides example use cases (tanks, pipes, containers). However, it doesn't explicitly differentiate from other volume calculators like calculate_cone or calculate_sphere among siblings.

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?

Advises using for tanks, pipes, or containers, and directs to list_bundles for related calculators. Lacks explicit when-not-to-use or comparisons to siblings.

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