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

Description includes the cost ($0.001), a behavioral trait not in annotations (none provided). However, it omits other potential side effects or safety information. Since annotations are absent, the cost is a valuable addition, but more detail would be ideal.

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?

One sentence that captures the core functionality and a critical behavioral detail (cost). No fluff, front-loaded verb, and resource. Every word earns its place.

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 absence of an output schema and zero parameter explanation, the description leaves significant gaps. An agent would not understand how to use the direction or decimals parameters correctly, nor what the return value looks like.

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 description adds no meaning beyond the input schema. Schema coverage is 0%, and the description does not explain the purpose of the three parameters (amount, decimals, direction). Without this, an agent must rely solely on parameter names.

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?

Description clearly states the tool converts USDC amounts between atomic and decimal units, with a specific verb and resource. It distinguishes from siblings by focusing solely on USDC conversion, which no other sibling tool addresses directly.

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 explicit guidance on when to use this tool versus alternatives. No mention of prerequisites or context. The description only states functionality without providing usage criteria.

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