get_account_nfts

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

No annotations are provided, so the description carries the full burden. It offers minimal behavioral context: 'from Solscan' implies a data source, but it does not disclose that this is a read-only operation, potential rate limits, pagination behavior, or what happens if the account has no NFTs or an invalid address.

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, efficient sentence that communicates the core purpose without any redundancy. It is appropriately concise for a straightforward read operation.

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 lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It fails to explain likely return structure, how to interpret the list of NFTs, or any edge cases. For a tool with two parameters and informational needs, this is insufficient.

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 0%, so the description must explain parameters. 'address' is implicitly covered by 'Solana account', but 'limit' is not mentioned at all. The description does not clarify the meaning or purpose of the optional limit parameter beyond what the schema name suggests.

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 verb 'Get', the resource ('NFTs held by a Solana account'), and the source ('from Solscan'). This distinguishes it from siblings like get_account_tokens (which could include non-NFT tokens) and get_account_nft_activities (which is about activity, not holdings).

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 is provided on when to use this tool versus alternatives such as get_account_tokens or get_account_nft_activities. The description merely states what it does without any context on selection criteria or exclusions.

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