Get NFT Issuer by Wallet

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds useful context by listing the returned fields (issuer name, category, website, verification status, domain proof) and by clarifying the registry-backed nature of the lookup. This is helpful but not exceptionally rich; it does not explain behavior on missing or invalid addresses.

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 compact and front-loaded. The first sentence states the core action; the second gives a concrete use case; the third lists the return fields. No wasted words or redundant restatements of the name.

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 one-parameter, read-only lookup with an output schema, the description covers the essential elements: what it does, when to use it, and what it returns. It could be more complete by contrasting with the sibling lookup tool and explaining not-found behavior, but these are minor gaps for a simple lookup operation.

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% and the parameter description already explains the wallet address format (r...) and purpose. The tool description does not add additional parameter-level details beyond what the schema provides, so it sits at the baseline.

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 a specific action ('Look up a registered NFT issuer by their XRPL wallet address') and resource (NFT issuer in the AgentTrust registry). It also describes the intended use case, but it does not explicitly differentiate itself from the similarly named sibling tool 'lookup_nft_issuer', so it misses the highest bar for sibling distinction.

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 gives clear context for when to use the tool ('verify the identity of an NFT's minting wallet' and check registry membership). It does not, however, state when not to use it or mention alternatives such as 'lookup_nft_issuer', so exclusion guidance is absent.

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