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

No annotations are provided, so the description carries the burden, but a deterministic unit conversion has a minimal behavioral footprint. It conveys the supported units and the directional semantics but says nothing about precision/rounding, determinism, or that omitting the target unit returns all units.

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?

A single front-loaded sentence with no filler; every word earns its place by naming the verb, resource, and unit domain.

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 100% schema coverage and an output schema present, return values and parameters need not be repeated. The description is complete enough for a simple conversion utility, with only mild gaps around precision and the optional-target default.

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%, so the enum for 'from'/'to', the optional-target behavior, and the value type are already fully documented in the schema. The description only restates the unit names and adds no meaning beyond the structured fields, making the baseline 3 correct.

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 (speed value) and enumerates the exact unit set handled, so the agent immediately knows the operation. It does not explicitly differentiate from siblings like convert_distance or convert_power, though the resource noun makes the separation self-evident.

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 gives no when-to-use, when-not-to-use, or alternative guidance. It is implied that this is the tool for speed conversions, but nothing addresses sibling selection or the case where a different dimension (distance, fuel economy) is needed.

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