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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds a small amount of behavior — exact conversion and support for arbitrary token decimals, plus a $0.005 cost hint — but it still does not disclose how results are returned or whether invalid inputs produce errors.

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 run-on phrase that front-loads a cost note ('Paid $0.005 USDC on Base or Solana') and then tacks on the purpose without clear separation. It is short, but the structure buries the actual semantics and reads malformed.

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?

With no output schema and no parameter documentation, the description must carry enough context for a correct call. It does not state what parse vs format do to the value, what units the input or output use, or what the response looks like, so an agent cannot confidently verify its call.

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. It only hints at the decimals parameter via 'arbitrary token decimals'; mode and value semantics are not explained, leaving an agent to infer parse/format behavior from enum names rather than from documentation.

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 core phrase 'exact decimal/base-unit conversion with arbitrary token decimals' states a specific conversion operation and target resource, distinguishing it from sibling encoding/hashing utilities. However, the description is preceded by the garbled cost phrase 'Paid $0.005 USDC on Base or Solana' and never explicitly ties the conversion to the parse/format modes in the schema.

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 given about when to use this tool instead of the many sibling utility tools, no exclusions are mentioned, and the only contextual hint ('Base or Solana') is ambiguous because it appears attached to the paid-cost phrase rather than as tool applicability.

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