volume_convert

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

With no annotations, the description fails to disclose important behavioral traits such as return format, error handling for invalid units, or whether the tool accepts abbreviations. The brief parameter descriptions do not cover these aspects.

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 concise with two sentences and a parameter list, front-loading the core purpose. It is well-structured but could be slightly more compact.

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?

Despite having an output schema, the description omits information about what the tool returns and does not explain error behavior or the full range of supported units. The minimal details are insufficient for a tool with three required parameters and no annotations.

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?

Given 0% schema coverage, the description adds basic meaning by naming the parameters ('Volume value', 'Source unit', 'Target unit'), but does not specify acceptable unit formats or provide a complete list of supported units beyond examples. Additional detail would be needed for full compensation.

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 'Convert between volume units' and lists specific units (liters, gallons, etc.), making the tool's purpose unambiguous. However, it does not differentiate from sibling tools like 'convert_units' that might also handle volume conversions.

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?

No guidance is provided on when to use this tool versus alternatives such as the general 'convert_units' or other conversion tools. The description only states the function without context about appropriate usage scenarios.

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