calculate_aquarium_volume

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

No annotations are provided, so the description must fully disclose behavior. It mentions inputs and returns but contradicts the actual schema by implying shape and radius parameters that do not exist, creating confusion.

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 short but contains inaccuracies that undermine clarity. The second sentence about shape and radius is misleading, reducing the overall conciseness.

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?

Although an output schema exists, the description omits important details like the substrate parameter and accurate input requirements. It does not fully describe the tool's capabilities or limitations.

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 the description should compensate. Instead, it introduces non-existent parameters (shape, radius) and fails to mention the substrate parameter. This misleads the agent about required inputs.

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 the tool computes aquarium water volume in liters and gallons, with specific use cases for fishkeeping, dosing, and stocking. It distinguishes itself from other volume calculators by referencing related 'animaux' calculators.

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 provides context for when to use (fishkeeping, dosing, stocking) and directs to list_bundles for alternatives. However, it lacks explicit exclusion criteria or 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.