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 states 'Get all NFTs' but fails to disclose that the default limit is 100, meaning it may not actually return all NFTs. It also does not mention pagination, network behavior, or error handling, creating a potential gap between expectation and actual behavior.

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 sentence that immediately conveys the core purpose with no filler or redundant wording. It is well-structured and front-loaded.

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?

The description is too minimal for the tool's context. It fails to mention the default limit of 100, making the claim of returning 'all NFTs' misleading. With no output schema and no annotations, it also omits return format, pagination, and network selection context, leaving the agent under-informed.

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 provides descriptions for all three parameters, giving 100% coverage, so the baseline is 3. The tool description adds minimal semantic value beyond restating that the account is an XRPL address; it does not clarify how limit or network affect the query or result.

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 retrieves all NFTs owned by an XRPL account, using a specific verb and resource. It distinguishes itself from siblings like get_nft_info (which targets individual NFTs) and other account-related getters.

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 conveys a clear purpose, so usage is implied, but it does not explicitly state when to use this tool versus alternatives. No exclusions or alternative recommendations are provided, leaving the agent to infer that this is for full NFT lists rather than specific NFT lookups.

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