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

Annotations already signal a non-read-only, non-destructive write with an open world; the description adds meaningful context by requiring prior ownership proof and by noting that limits are scoped per verified identity rather than globally. No contradictions with annotations. It does not detail idempotency/duplicate behavior or exact side effects, but the annotation set lowers that burden.

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 focused sentences, front-loaded with the action and prerequisites. The second sentence adds a material business rule with no waste; every clause has signal.

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?

The description provides the precondition, permitted roles, and scoping rule, and the schema supplies required patterns and enum. However, it is a creation/write tool with no output schema, and the description does not mention expected return value, idempotency semantics, or failure/duplicate behavior, leaving clear gaps.

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?

With 0% schema description coverage, the description must carry parameter meaning. It explains the role enumeration (BUYER/SELLER) and points to EVM ownership proof, which maps to ownershipProof and address. It does not elaborate on idempotencyKey or displayName, though those are fairly self-explanatory; the compensation is partial but not missing.

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 uses a specific action ('Create or bind') and a specific resource ('permitted BUYER or SELLER wallet'), and adds the key contextual scope of the authenticated agent and EVM ownership proof. This distinguishes the tool from read/support siblings like get_wallet and other wallet-related operations.

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 states the precondition 'after EVM ownership proof' and clarifies the wallet role scope, making the intended use case clear. It does not explicitly name alternatives or say when not to use this tool, but the usage context is strong enough that an agent can decide correctly.

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