convert_speed

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered without the description's help. The description adds nothing else: no supported unit set, no rounding/precision behavior, no statement about accepted aliases (e.g. "km/h" vs "kph"). Beyond the name it contributes essentially no behavioral context.

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?

One short, front-loaded sentence with no filler or redundancy. The problem is under-specification rather than verbosity, which is captured in the other dimensions.

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?

For a 3-required-param conversion tool with no output schema and no enum constraints, the description should enumerate supported units and note the return behavior. None of that is present, so an agent cannot construct a valid call with confidence.

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 there are three required parameters (value, from, to) with no enums and no descriptions. The description must therefore carry the unit vocabulary, and it does not — 'from' and 'to' are bare strings with no hint of valid values, which is the single most important thing to know before calling.

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 and resource family ("Convert between speed units"), which cleanly separates it from convert_length, convert_weight, pressure_convert, and other unit-family siblings. It stops short of naming the supported units, so an agent cannot tell the scope of the conversion domain from the description alone.

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?

Usage is only implied: an agent infers it should call this when a speed conversion is needed and pick a different convert_* sibling for other unit families. There is no explicit when-to-use, no mention of valid unit values, and no exclusion or alternative named.

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