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: it discloses the scope model, the login-vs-proven distinction, the rule that giving is allowed from a login wallet on any chain but from a proven wallet only on EVM, and that proving requires an authorization from the login wallet. What it omits is any statement that this call is side-effect-free/read-only and how large the response may be.

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 core definition is front-loaded in the first sentence, but the rest of the text drifts into wallet-proving workflow that belongs to the sibling tools (wallet_proof_message, prove_wallet), making the description longer and denser than an identity call warrants.

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?

For a zero-parameter, no-output-schema tool, the description is essentially complete: it names the fields returned and the permission model that determines what the caller may do. Only the read-only nature and any auth-failure behaviour are unstated.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. Its explanation of the returned `login` and `proven` fields is a bonus rather than a parameter clarification.

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 makes clear this reports the identity behind the API key: its scopes (read/taker/maker) and, per chain, `login` (paid wallet) and `proven` (proved wallets). It is specific about the returned resource and explicitly references the sibling tools (wallet_proof_message, prove_wallet) used for the adjacent workflow, though it never states in a single clean clause that this is a read of the current credential.

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 gives concrete when-to-use guidance: 'Verify auth, and check what you may give before quoting,' and explains the alternative path for trading on non-EVM chains via wallet_proof_message then prove_wallet. There are no explicit when-not-to-use exclusions, but the routing to siblings is clear.

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