math_fuel_consumption_calculator

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

No annotations provided; description claims both conversion and trip fuel/cost calculations, but the input schema only supports a single value conversion with no fields for trip inputs, leading to a significant behavioral gap.

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 but includes extraneous 'Menu ID' and a pointer to another tool for full guidance, which may reduce clarity.

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 no annotations, no output schema, and 100% required parameters with no schema descriptions, the description is insufficient for an agent to correctly use the tool, especially for trip calculations.

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 description coverage is 0%, and the description provides no information about the purpose or valid values of parameters operation, value, fromUnit, toUnit.

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 it is a fuel consumption calculator that converts between US mpg, UK mpg, L/100km, and km/L, and can calculate trip fuel and cost. It distinguishes from sibling conversion tools by focusing on fuel consumption, but does not explicitly differentiate.

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 for fuel consumption conversion and trip calculations, but lacks explicit guidance on when to use vs alternatives, and does not explain how to invoke trip fuel vs conversion.

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