convert_volume

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

With no annotations, the description carries the full burden. It indicates a non-destructive conversion but lacks details on error handling, return format, or side effects. The description adds minimal behavioral insight beyond what the unit list implies.

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 extremely concise: two sentences covering purpose, units, use cases, and a related tool reference. No redundant information.

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 the simplicity of the tool and the presence of an output schema, the description is fairly complete. It covers the core conversion functionality and use cases, though the return format reference is vague ('{input}') and could be more precise.

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 parameter descriptions. The description lists inputs and mentions the return value as '{input}', but does not add significant meaning beyond the schema. The enumeration of units in the description provides some context, but it's already in the schema.

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 uses a clear verb 'Convert' and specifies the resource 'volume' with a comprehensive list of units (L, mL, cL, fl_oz, etc.). It also states use cases ('cooking and science'), effectively distinguishing it from sibling tools like convert_angle or convert_speed.

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 explicitly states 'Use for cooking and science,' providing context for when to use the tool. It also recommends seeing list_bundles for related converters, giving some guidance on alternatives, though it could be more explicit about when not to use this tool.

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