Get NFT Issuer by Wallet

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description's only added behavioral detail is the registry context, which hints that unregistered wallets are a possible outcome, but it never states what happens on a miss, whether auth is needed, or any rate limits.

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?

Front-loaded one-line purpose followed by a use case and a returns list; no filler prose. The 'Returns:' block largely restates the output schema, which is the only wasted line.

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?

With an output schema present and annotations covering safety, the description needn't enumerate return fields, and it covers purpose, use case and scope adequately. A missing note on the not-found/unregistered case is the only real gap.

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?

Single parameter with 100% schema description coverage, so the schema fully documents the wallet_address format (r...). The description adds no format, validation, or lookup-key nuance beyond the schema, which is the expected baseline at full coverage.

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?

States a specific verb (look up) and resource (registered NFT issuer) keyed on an XRPL wallet address, which is a distinct lookup axis from the sibling lookup_nft_issuer. It does not name that sibling or otherwise explicitly contrast itself, so it stops short of a 5.

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?

Gives a clear use case — verifying whether an NFT's minting wallet belongs to a known, verified organisation in the AgentTrust registry. It provides no exclusions or alternative-tool routing (e.g. when to use lookup_nft_issuer or verify_wallet_domain instead), so it is context without boundaries.

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