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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real behavioral context beyond them: the result is read live from the chain rather than an index, and 'unrevoked' signals that revoked tokens are treated as not held. It does not cover failure modes (e.g. unknown collection, unsupported chain/wallet pairing), which keeps it from a 5.

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?

Two compact sentences: the capability first, then the one non-obvious parameter. No filler, nothing buried, and the clarification is placed after the core statement.

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 no output schema, the description still conveys that the answer is a boolean hold/no-hold verdict and that it is fetched live, which is the essential return semantics. Missing only edge-case behavior for invalid or mismatched chain/collection inputs.

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 only 33% (wallet documented, chain only an enum, collection bare), and the description compensates by defining collection as an EVM contract address or a Solana group mint — the exact ambiguity an agent would otherwise hit. Chain and wallet semantics are left to the enum and schema, so it is not exhaustive.

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 names a specific verb-and-resource: checks whether a wallet holds an unrevoked, non-transferable token of a collection, read live from chain. That is far more precise than the title alone and separates it from cached/indexed siblings like my_soulbound_collections or list_pending_soulbound, though no sibling is named explicitly.

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?

There is no statement of when to use this versus list_pending_soulbound, my_soulbound_collections, or my_soulbound_usage. The phrase 'read from the chain' faintly implies a live on-chain check rather than a cached lookup, but no exclusion or alternative is offered.

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