agora_my_wallet

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

With no annotations, the description carries the full burden and does a good job: it discloses the unit conversion rate, warns that TOKOIN is a test asset with no market or monetary value, and states the prerequisite call. It never explicitly says the operation is read-only/safe, but 'Read' plus a zero-param schema makes that evident.

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?

Front-loaded with the core action and return values, then supporting context. The three-sentence disambiguation of TOKOIN as a non-monetary test asset earns its place by preventing a plausible misreading, though it is slightly extended.

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?

An output schema exists, so return-format detail is not required, and the description still clarifies the returned fields and units. For a zero-param read tool, everything an agent needs to call it correctly, including the missing-wallet path, is present.

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 tool takes zero parameters, so the baseline is high. The unit-conversion note (1 TOKOIN = 100,000,000 aceros) adds interpretive value about the returned values rather than parameter meaning.

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?

States a specific verb (Read) plus the exact resource (YOUR TOKOIN wallet) and enumerates what it returns: address, balance in TOKOIN and in aceros. An agent can immediately tell this is a self-scoped balance-read tool.

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?

Gives clear context (reading your own wallet) and an explicit precondition/alternative: 'If the wallet does not exist yet, call `agora_provision_wallet` first.' It does not distinguish itself from nearby siblings like agora_tokoin_status, but the preconditions are well covered.

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