volume_converter

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the conversion action and input names, but does not mention the return format (e.g., a number), error handling for invalid units, case sensitivity, or any side effects. As a simple read-only conversion, this is a minimal gap, but the description does not explicitly say it is safe or how it behaves on failure.

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 sentences, front-loads the purpose and unit list, and has zero wasted words. It efficiently conveys the tool's scope and input requirements without redundancy.

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?

The description covers the core purpose, input parameters, and valid unit values. However, it does not specify the output format (e.g., a numeric result) or describe error behavior for invalid inputs. Given that there is no output schema and no annotations, these details would help an agent call the tool correctly and interpret results. The description is adequate for a simple converter but leaves some behavioral gaps.

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?

The schema has 0% description coverage, so the description must compensate. The first sentence lists all valid unit strings for the 'from' and 'to' parameters, which is essential information not present in the schema. This adds meaning beyond the schema, though it does not clarify the 'value' parameter beyond its type (number) or explain that from and to must be one of the listed strings. The unit list is a significant contribution.

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 states a specific verb ('Convert') and resource ('volume'), and lists the supported units (ml/l/cup/tbsp/tsp/floz/pint/quart/gallon), which clearly distinguishes it from sibling converters like length_converter or weight_converter. The unit list is concrete and unambiguous, so an agent can immediately identify this tool for 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?

The description implies usage through the phrase 'Convert volume' and the listed units, but it provides no explicit guidance on when to use this tool versus other converters, nor any exclusions (e.g., 'for length use length_converter'). The input line 'Input: value, from, to' only names the parameters and does not give context about selection criteria.

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