convert_length

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs conversions but does not describe how it handles invalid units, rounding, precision, errors, or the format of results. For a tool with no annotations and no output schema, this leaves significant gaps in understanding its behavior.

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 brief and to the point, using a single sentence to convey the core functionality. The domain/category note is slightly redundant but not wasteful. It is front-loaded with the main purpose, though it could be more structured with usage hints.

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 the tool's complexity (3 parameters, no annotations, no output schema), the description is insufficient. It lacks details on parameter usage, error handling, result format, and differentiation from siblings. For a conversion tool, users need to know valid units and output expectations, which are not addressed.

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?

The input schema has 0% description coverage, so the schema only defines parameter types without meaning. The description mentions units like meters and feet but does not specify valid unit strings, formats, or examples for the 'from_unit' and 'to_unit' parameters. It adds minimal semantic context beyond the schema, failing to compensate for the low coverage.

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 clearly states the tool's purpose: converting length between units like meters, feet, inches, etc. It specifies the verb ('convert') and resource ('length'), making the intent unambiguous. However, it does not explicitly differentiate from sibling conversion tools (e.g., convert_area, convert_volume), though the domain/category hints at its scope.

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 provides no guidance on when to use this tool versus alternatives. It lists sibling tools like convert_area and convert_volume but does not explain how to choose between them (e.g., for length vs. area conversions). There is no mention of prerequisites, constraints, or typical use cases.

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