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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the operation is read-only, error handling, or constraints like unit format validity. Simply stating 'Convert units' is insufficient for an agent to anticipate 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 a single, front-loaded sentence that efficiently conveys the tool's purpose. Every word is necessary, and it avoids redundancy. It could be slightly more structured by separating categories, but overall it is concise.

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 output schema, no annotations, and low schema coverage, the description is severely incomplete. It fails to explain the output format, error cases, or supported unit range. The agent would likely need additional context or trial-and-error to use this tool correctly.

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?

With only 25% schema description coverage (only the 'category' field has a description), the description adds minimal meaning. It lists categories but does not clarify the format or accepted values for 'from_unit' and 'to_unit' (e.g., case sensitivity, abbreviation vs. full name). This gap leaves the agent underinformed.

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 converts units and lists six categories (length, weight, temperature, data, speed, time), distinguishing it from sibling tools like currency_convert and time_convert. However, it could be more specific about the scope (e.g., 'Convert physical quantities between units').

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. With many conversion siblings (e.g., currency_convert, time_convert), the description should explicitly state that currency and time are not covered (since time_convert exists) and mention that unit_list provides supported units. The lack of such context hinders correct selection.

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