get_wallet_info

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

Discloses it is a read operation returning wallet info. No annotations, but description is sufficient for basic behavioral understanding. No mention of authentication or rate limits, but acceptable for this simple tool.

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 main function, no redundant words. Efficient and easy to parse.

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?

No output schema provided. The description lists returned items (address, balances of specific tokens) but does not specify data format (e.g., decimal vs raw, structure). Could be more complete for an agent to interpret results.

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 has 100% coverage, describing chain_id with examples and default. Description adds 'across chains' but does not elaborate further on parameter format or behavior beyond 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 clearly states it returns the agent's wallet address and token balances across chains, listing specific tokens. This distinguishes it from siblings like get_token_price or get_transaction_status.

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?

Explicitly tells to call this before executing transactions, providing clear context. However, it does not specify when not to use or mention alternative tools.

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