convert_to_base_unit

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

The description only states the core action without disclosing any behavioral details such as how decimals are applied, return format, precision handling, or error conditions. The openWorldHint annotation provides minimal safety context and does not compensate for the lack of behavioral transparency.

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, direct sentence that immediately communicates the core function. It contains no unnecessary words or redundancy, making it appropriately concise and well-structured.

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 the tool has no output schema and a very short description, the agent is left without information about the return value, conversion formula, or edge cases. The presence of similarly named siblings increases the risk of incorrect selection. The description does not sufficiently compensate for this lack of context.

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 provides descriptions for all three parameters (amount, decimals, chainId), achieving 100% coverage. The tool description itself adds no additional parameter-level meaning beyond what the schema already conveys, so the baseline score of 3 is appropriate.

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 an ERC20 token amount to its base unit, using a specific verb and resource. However, it does not distinguish itself from the sibling tool 'convert_to_base_units' (plural), which appears to have an identical purpose.

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 the similarly named siblings 'convert_to_base_units', 'convert_from_base_unit', or alternatives. There is no mention of context, prerequisites, or exclusion scenarios.

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