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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered without description help. The description does add real behavioral context by naming the return payload (converted value plus the factor) and tying results to the site's calculator factors, but it omits anything on failure modes, unknown units, or limits.

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 the core verb first and the example and return value trailing. It is efficient, though the final clause stacking factor provenance and return shape makes it slightly dense.

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?

An output schema exists, so the description is not obliged to explain return values, and the annotations carry the safety profile. Still, for a five-parameter tool with 40% schema coverage, the lack of unit-format and dimension-disambiguation guidance leaves gaps an agent would hit in practice.

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 only 40% across five parameters, so the description is expected to compensate and does not. It illuminates 'value', 'from' and 'to' only through an example, and says nothing about valid unit strings (the 40-character maxLength), how 'dimension' resolves ambiguous units, or how 'detail' changes output.

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 (converts a value from one unit to another) with a concrete example (2 m³ to cubic yards). It also hints at the differentiating trait versus generic calculators by promising 'the exact factor the site's calculators apply,' though it never names calculate or solve_backwards, so the sibling distinction is only implied.

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 prefer this tool over calculate, solve_backwards, or the many other numeric siblings, nor any prerequisite or exclusion. An agent must infer usage entirely from the tool name.

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