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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds value by stating what is returned (issuer name, category, website, verification status, domain proof), which is not present in annotations. No contradiction with annotations.

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 concise, with a clear single sentence followed by a list of returned fields. It wastes no words and is front-loaded with the core action. Could be slightly improved by being even more terse, but the structure is effective.

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 low complexity (one parameter, clear purpose), the description is complete. The output schema exists and the description enumerates the returned fields, which reduces the need for detailed return value documentation. The annotations cover safety and behavior well.

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 coverage is 100% with one required parameter. The description reiterates the parameter's purpose (wallet address for lookup) but does not add new semantic details beyond the schema description. Since schema coverage is high and only one parameter, the baseline of 3 is appropriate, but slight improvement because description explains what happens with the parameter.

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 it looks up an NFT issuer by wallet address, specifies the resource (XRPL wallet address) and the purpose (verify identity of an NFT's minting wallet against a registry). It distinguishes itself from siblings like lookup_nft_issuer by specifying the lookup key and the registry context.

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 explicitly instructs to use this tool to verify whether an NFT's minting wallet belongs to a known, verified organization. It implies a specific usage scenario but does not explicitly state when not to use it or alternatives; however, the context is clear enough for an agent to infer appropriate use.

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