Convert units

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

Annotation readOnlyHint=true is consistent with a pure conversion tool. The description adds that conversions are exact, implying no rounding or approximation. However, it doesn't disclose input/output format details (e.g., value as string representing a number, decimal support), which are behavioral traits beyond annotations.

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?

Extremely concise single sentence that front-loads the core purpose. Every word earns its place with no redundancy.

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 2-param tool with no output schema, the description is minimal. It should clarify input format (e.g., decimal string) and possibly return format. The annotations help by confirming read-only nature, but the description leaves gaps in usage and parameter details.

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. The listed unit pairs partially compensate by implying the 'unit' parameter should be one of those units, but the 'value' parameter is not addressed at all (format, precision, etc.). Baseline 3 is appropriate given partial compensation.

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?

Clear verb 'conversion' and specific resources (cryptocurrency units). The listed unit pairs (wei/gwei/ether, sat/btc, lamport/sol) clarify scope, but the description doesn't explicitly distinguish from siblings like gas_prices or get_chain.

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 on when to use this tool versus alternatives. The description states what it does but not the context or conditions for use. An agent must infer from the name and unit pairs alone.

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