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

With no annotations provided, the description carries the full burden and does so well. It discloses that the tool returns a nonce and message string, requires signing with a Solana wallet, must be followed by verify_login_signature, and that nonces expire after 5 minutes. This is meaningful behavioral context beyond the schema.

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 description is compact and front-loaded: it opens with the legacy warning, then states the workflow and expiry. Every sentence earns its place, with no repetition or filler.

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 tool with no output schema, the description is complete. It explains what is returned, what the agent must do next, how long the nonce is valid, and how this tool relates to the modern alternative flow.

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%, so the baseline is 3. The description adds only a minor behavioral tie-in by noting the wallet must sign the message, but it does not add new parameter-level meaning beyond the schema's own description of walletAddress.

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 clearly identifies the tool as the first step of dashboard authentication, returning a nonce and message to sign with a Solana wallet. It also positions it as the LEGACY wallet flow, distinguishing it from create_account and launch_campaign for new integrations. This is specific and actionable.

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 explicitly states that new integrations should use create_account and launch_campaign instead, and describes the exact workflow: call this tool, sign the message, then pass it to verify_login_signature for a session token. The 5-minute expiry also gives temporal guidance.

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