convert_length

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's safety burden is light. However, it adds nothing beyond them: no supported unit identifiers, no precision/rounding behavior, no error behavior for invalid units. With annotations covering safety, the description still leaves the operational profile blank.

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 zero padding. It is efficient but so terse that brevity shades into under-specification.

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 converter with three required parameters, no schema documentation, and no output schema, the description should at minimum name supported units or output shape. Neither is present, so an agent cannot know whether 'to' expects 'km', 'kilometers', or a unit id.

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 says nothing about value, from or to. Critically, the valid unit strings accepted by 'from'/'to' are undocumented in both the schema and the description, which is the single most important thing an agent needs to call this correctly.

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?

Names a specific verb and resource ('Convert between length units'), which cleanly separates it from siblings like convert_volume, convert_weight and convert_temperature. It stops short of 5 because it doesn't scope what 'length units' covers.

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?

There is no statement of when to use this vs. the many convert_* siblings, nor any prerequisite or exclusion. The agent must infer from the tool name alone that this handles length rather than area, volume or wavelength.

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