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

With no annotations, the description carries the full burden and does well: read-only, no signature required, callable unauthenticated via x402 with payment instructions in the 402 body, or via a free-tier IDENTITY_API_KEY. It stops short of stating rate limits, failure modes, or cost specifics beyond the 402 mechanism.

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-loads the purpose, then the auth/payment model, then the arg, with no filler. The parenthetical about x402 payment instructions is the one slightly heavy clause but it is genuinely informative.

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?

An output schema exists, so return values need not be explained; the description covers purpose, the two access paths, and the lone parameter. What remains unstated — error behavior on an expired or missing assertion — is minor for a simple read check.

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 0% and the single property is documented only as 'string', so the description must compensate. It does so by specifying the expected format ('The 0x wallet address to check'), which is real added meaning for an agent constructing the call.

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 and resource ('check whether a wallet holds a valid, unexpired Wicked Identity assertion') and immediately scopes it as the read-only, third-party variant, which separates it from the write-side siblings like identity_register and identity_submit_response without opening any schema.

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?

It says this is the check any third party can run on someone else's wallet with no signature, which tells the agent when this read path applies versus the challenge/nonce flow. It does not explicitly name identity_get_challenge or identity_get_nonce as the alternatives, so the routing guidance is clear but not exhaustive.

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