format_wei_to_ether_precise

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: lossless conversion, arbitrary precision, avoidance of float precision loss, and the payment cost (0.005 USDC on Base L2). However, it does not describe failure modes, output format, or how errors are handled. This is adequate but not exhaustive for a conversion tool.

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 sentence with a parenthetical, front-loading the core purpose and key differentiators. It wastes no words and the cost note is efficiently included. It is appropriately sized and immediately scannable.

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?

The tool is a specialized conversion with a payment component, but the description omits essential details: the exact format of the payload (how to specify wei, whether ether or USDC is selected), the output structure (since there is no output schema), and specifics about the payment process beyond the cost. An agent would struggle to invoke it correctly without additional documentation.

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 describes both parameters generically: payload as 'Input parameters or JSON string payload' and paymentSignature as 'Base L2 USDC micropayment signature or transaction hash'. Although schema coverage is 100%, these descriptions are vague and do not specify what the payload should contain (e.g., wei amount, target currency). The tool description also does not clarify the expected payload structure, leaving agents without enough guidance to construct valid input.

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 states a specific verb (convert) and resource (wei to ether/USDC), and highlights key differentiators: lossless, arbitrary-precision, and avoidance of JS 64-bit float precision loss. This clearly distinguishes it from sibling conversion tools like calculate_compound_yield or calculate_dex_slippage_bounds, and the parenthetical cost note adds practical specificity.

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 when precision-critical wei-to-ether/USDC conversion is needed, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites beyond the payment requirement. There is no comparison to other conversion tools, leaving the selection partly to inference.

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