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

No annotations provided, but the description explicitly states the return format as {result, from_unit, to_unit, formula}. This adds behavioral context beyond a simple conversion claim. No mention of side effects or auth, but conversion is inherently read-only.

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?

Two sentences with no fluff. First sentence states the action, second lists supported domains and return structure. Efficient and front-loaded.

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 conversion tool with 3 required parameters and no output schema, the description lacks essential details on valid unit formats and input constraints. An agent may fail to provide correct units without additional knowledge.

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 does not explain parameter formats or valid unit strings. It only lists categories, which adds some context but is insufficient for an agent to know expected unit names (e.g., 'meters' vs 'm').

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 between units and lists specific categories (length, weight, temperature, area, volume). It distinguishes itself from sibling tools which are financial calculations or health checks.

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 implies usage for unit conversion within the listed categories but does not provide explicit when-to-use or when-not-to-use guidance. Sibling tools are distinct, so no confusion.

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