get_wallet_balances

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

No annotations are provided, so the description carries full burden. It discloses that it uses the wallet address from WALLET_PRIVATE_KEY and returns stablecoin holdings, but does not mention pagination, the restriction to querying only your own balances (though mentioned in schema), or any error behavior.

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?

Two sentences, front-loaded with purpose. Each sentence adds context: what it returns and address source. No unnecessary words.

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?

For a simple read-only tool with no output schema, the description covers purpose, return type ('stablecoin holdings with amounts and metadata'), and default address behavior. It lacks explicit return structure or pagination details, but schema covers parameters. It's reasonably complete for selecting this tool over siblings.

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 coverage is 100% with descriptions for page, page_size, and wallet_address. The description adds no extra parameter semantics beyond restating the configured wallet behavior, so baseline 3 applies.

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 explicitly states 'Get token balances for the configured wallet' with a clear verb and resource. It further specifies it returns 'all stablecoin holdings with amounts and metadata,' which distinguishes it from sibling tools like get_exchange_balance and get_wallet_info.

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 description does not provide explicit when-to-use or alternative guidance. It implies usage for checking stablecoin balances in the configured wallet, but does not exclude other balance-related tools or state conditions for use.

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