create_bridge_wallet_challenge

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

With no annotations, the description carries the full burden and does so richly: no state is minted or changed, the challenge is not single-use but harmless because the message is bound to the account and address, message is opaque and must be echoed verbatim, nonce is informational and must not be signed, 503 wallet_registration_unavailable means registration is disabled, and API credentials are required.

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?

Long but almost every clause carries non-obvious operational information (opaque message handling, nonce trap, non-single-use semantics, 503 meaning, auth requirement), and the primary action is front-loaded in the first sentence.

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 single-parameter, no-annotation, no-output-schema tool, the description supplies the return payload (message, expires_at), the downstream call, idempotency semantics, error behavior, and auth needs. Nothing an agent needs to invoke it correctly is missing.

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% for the single address parameter, and the description reinforces its role ('the message is bound to ... address') without adding format or validation detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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 — 'Step 1 of registering a withdrawal wallet' that 'returns the exact message to sign' — and explicitly names its companion step, register_bridge_wallet. An agent can distinguish it from register_bridge_wallet and create_wallet 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?

Gives explicit routing: sign the message and pass it plus the signature to register_bridge_wallet, or, for the wallet create_wallet made, omit the signature and let the server sign. It also states it is safe to call before deciding to register, and that retrying on a 503 is pointless.

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