spl-token_getTokenAccounts

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

No annotations provided. The description mentions listing with balances and metadata but does not disclose default behavior (e.g., whether zero-balance accounts are included by default) or return format. Lacks behavioral details beyond the obvious read operation.

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?

Single sentence, front-loaded with key action and resource. No wasted words; appropriately concise for a simple listing tool.

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 basic listing tool with good schema coverage and no output schema, the description is adequate but lacks information on default filtering (e.g., whether zero balances are included by default) and any pagination or limit behavior. Could be more complete.

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 both parameters (wallet and showZeroBalance). The description does not add additional semantic context beyond what the schema already provides, so baseline score of 3 is appropriate.

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 the tool lists all SPL token accounts for a wallet with balances and metadata. It uses a specific verb (list) and resource (token accounts for wallet), which distinguishes it from sibling tools like getBalance or rugCheck, though it doesn't explicitly name alternatives.

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?

No guidance on when to use this tool versus alternatives like getBalance or rugCheck. The description only states what it does without providing context for selection.

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