batch_conversion

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only mentions 'in a single call' (a minor optimization hint) but does not reveal error behavior, precision, unit validation, or whether the operation is read-only. This is a significant gap for a conversion tool.

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 a single, front-loaded sentence with no wasted words. It is sufficiently concise and easy to parse.

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 four required parameters and an output schema, the description is minimal. It does not mention how the output is structured (though output schema exists), nor does it address batch limits or error cases. Overall, it is insufficient for an agent to confidently use this tool without further inference.

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, and the description does not compensate. It does not explain the relationship between values, from_unit, to_unit, and category, nor does it clarify valid unit strings. The enum for category is in the schema, but the description adds no meaning beyond what the schema already provides.

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 action (convert) and the resource (multiple values between units), and the phrase 'in a single call' distinguishes this batch operation from the sibling unit_conversion tool. While it doesn't name the sibling, the scope is specific and unambiguous.

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 batch_conversion versus unit_conversion. The description does not state that this should be used for multiple values or that single conversions should go to unit_conversion, leaving the agent to infer without explicit direction.

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