solanaGetAssetsByOwner

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions returning assets (tokens, NFTs) but omits critical details such as pagination behavior, rate limits, output format, or how parameters like sortBy affect results. This leaves significant gaps for an agent.

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 a single concise sentence that effectively front-loads the purpose. Every word is meaningful, and there is no redundant or extraneous content. It could be slightly more informative without losing conciseness, but it is well-structured.

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?

Given the tool's complexity (7 parameters, nested sortBy, pagination, no output schema), the description is overly minimal. It fails to integrate parameter details, explain pagination, or clarify output expectations. The agent would need to infer too much from the schema alone.

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 description coverage is 100%, so the baseline is 3. The description does not add meaningful context beyond the schema parameter descriptions; it mentions 'tokens, NFTs' but does not elaborate on how parameters like sortBy or pagination work. Thus, it meets the baseline but does not exceed.

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 the verb (Get), resource (Solana assets), and scope (owned by a specific wallet address). It uses specific terms 'tokens, NFTs' and contrasts with sibling tools like solanaGetAssetsByAuthority, making it clear and distinctive.

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 provides no guidance on when to use this tool versus alternatives like solanaGetAssets or solanaSearchAssets. It does not mention prerequisites, typical use cases, or when to avoid this tool, leaving the agent without decision-making context.

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