acedatacloud_refresh_coin_info

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It implies a mutating operation ('refresh') and a verified-wallet prerequisite, but it does not disclose the confirm gate, on-chain side effects, authentication requirements, or what changes after a successful refresh.

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, front-loaded sentence with no filler. Every word adds meaning, making it highly 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?

With an output schema and 100% schema coverage, the description does not need to explain return values or parameter formats. However, it lacks guidance on when to use it and does not describe the confirm behavior or side effects, leaving some important context missing.

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 100%, with both coin_info_id ('CoinInfo UUID') and confirm ('Must be true to refresh on-chain balance') already described clearly. The tool description adds only 'verified wallet's ACE balance' as context, which does not materially improve parameter understanding beyond the schema.

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 action ('Refresh') and resource ('a verified wallet's ACE balance'), which clearly defines what the tool does. It also distinguishes this from sibling read-only tools like acedatacloud_get_balance or acedatacloud_get_wallet_summary by focusing on the refresh/update action.

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 verb 'refresh' implies when it should be used, and 'verified wallet' hints at a prerequisite, but there is no explicit guidance on when to use this tool versus reading balances with get_balance/get_wallet_summary, nor any exclusions or alternative tool references.

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