length_conversion

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

No annotations are provided, so the description carries full burden. It only states the conversion action without disclosing behavioral traits like error handling, supported unit formats, precision, or return format. This leaves critical operational details unspecified for a tool with three parameters.

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, efficient sentence in Chinese that directly states the tool's function. It's front-loaded with the core purpose, though it could be more structured by including key details without sacrificing brevity.

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?

Given no annotations, 0% schema coverage, no output schema, and three parameters, the description is incomplete. It doesn't explain what the tool returns, how errors are handled, or provide enough detail to use the tool correctly beyond the basic concept of length conversion.

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%, so the description must compensate. It mentions 'length units' which gives some context for from_unit and to_unit, but doesn't explain what units are valid, their syntax, or the meaning of value beyond being a number. This is inadequate for three undocumented parameters.

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 '在不同长度单位之间进行转换' (converts between different length units) states the general purpose but lacks specificity about what length units are supported or how the conversion works. It distinguishes from siblings like area_conversion or volume_conversion by focusing on length, but doesn't clarify scope beyond that.

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 this tool versus alternatives like speed_conversion or weight_conversion. The description implies it's for length units only, but doesn't mention prerequisites, limitations, or comparison to other conversion tools in the sibling list.

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