Get Solana Portfolio

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

Annotations already declare this as read-only, idempotent, non-destructive, and open-world. The description adds useful behavior context by clarifying that it returns the full portfolio structure, not just a balance, and that the agent should inspect specific fields like tokens[].symbol or nativeBalance for different user intents.

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?

The description is well-structured and front-loaded: purpose first, usage guidance second, then args, return shape, and examples. Every section adds decision-relevant value, and the examples map natural-language questions to the correct response fields.

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?

There is no output schema, so the description compensates by providing a detailed JSON response shape covering address, native balance, token entries, and total value. Combined with the sibling distinction and clear parameter documentation, nothing essential is missing for an agent to invoke this tool correctly.

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 input schema fully documents the single optional network parameter, including the enum values and default. The description repeats this information but adds no deeper semantics beyond what the schema already provides, so baseline 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 uses a specific verb and resource: returns the full Solana token portfolio including SOL and SPL tokens with USD values. It also distinguishes itself from monei_get_wallet by stating its broader scope, so an agent can clearly tell which tool fits the request.

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?

It explicitly says to use this tool when the user wants a breakdown of their Solana holdings and points to monei_get_wallet for a simple balance check. This direct when-to-use and when-not-to-use guidance is exactly what agents need to disambiguate between siblings.

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