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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the unit set and a placeholder "Returns: {input}" that conveys nothing about behavior, so it earns a baseline 3 rather than more.

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?

Three short sentences, front-loaded with the unit scope before the use case and cross-reference. No filler, though the "Returns: {input}" clause is a wasted placeholder that adds no 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?

With an output schema present, return values need not be described, and annotations cover safety, so the remaining needs are unit coverage and usage context — both present. The only real gap is sibling differentiation against the many adjacent conversion/volume tools.

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 100% with enums on from/to, so the schema already documents all three parameters. The description restates the parameter names and unit list (in a slightly different casing than the enum values) but adds no syntax, default, or rounding semantics beyond 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?

States a specific verb (Convert) and resource (volume) and enumerates the nine supported units, which makes the tool's scope unambiguous. However, it does not differentiate itself from overlapping siblings such as convert_cooking, calculate_cooking_conversion, or calculate_volume, so an agent must infer the boundary itself.

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?

"Use for cooking and science" gives a domain hint but no explicit when-to-use/when-not-to-use rule and no named alternative. Given the dense set of sibling converters and volume calculators, the agent gets implied but not actionable routing guidance.

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