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

With no annotations present, the description carries the behavioral disclosure burden. 'List' clearly implies a read-only operation and the token standard scope is explicit, but it does not mention behavior around zero balances, pagination, ordering, or whether NFTs are excluded beyond the SPL/Token-2022 qualifier.

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?

A single, front-loaded sentence that conveys the action, the specific token standard, and the address-space nuance. Every word earns its place with no redundancy.

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 one-parameter read tool with no output schema, the description covers the essential purpose, the exact token standards, and the chain/address context. Minor omissions like result ordering or zero-balance handling are acceptable given the tool's simplicity.

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 0%, so the description must compensate. It clarifies that 'wallet' refers to an X1/Solana address and notes the shared address space, which adds meaning beyond the bare schema. It does not specify expected address format or encoding, but the single parameter is self-explanatory.

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 verb ('List'), a precise resource ('SPL+Token-2022 token balances'), and a clear scope ('for a given X1/Solana wallet'). It clearly separates this from general wallet or token-lookup tools in the sibling list.

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 intended use is implied: call this when you need the token-2022/SPL holdings of a specific wallet. However, it provides no explicit guidance about when not to use it or which sibling tool might be better for related needs like wallet profile or token lookup.

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