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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context: the signature-verification mechanism, the operator-authorization requirement, and the explicit boundary that no token transfer/approval is authorized. This clarifies the scope of the state change beyond what annotations alone convey.

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?

Three short sentences with no wasted words. The core action is front-loaded, and the subsequent sentences add security context and scope boundaries. Every sentence contributes necessary information.

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?

Covers the core binding mechanism, the authorization requirement, and the non-effect on token transfers. Missing details include the role of request_id (presumably correlating to a wallet_message call) and the exact prerequisite flow for obtaining the wallet_message result. With no output schema, return-value behavior is undocumented but secondary to the request_id gap.

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 description coverage is only 25%, so the description must compensate. It clarifies that address should be an operator-authorized wallet and that signature is a signature over the exact wallet_message result. However, request_id remains unexplained in both schema and description, and the description does not cover all parameters. Partial compensation for the low coverage.

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 'Bind' with resource 'wallet' and the precise mechanism 'verifying its signature of the exact wallet_message result.' This distinguishes it from sibling speedbot_exchange_wallet_message (which presumably provides the sessage to sign) and from token-transfer tools. The title 'Exchange: Bind wallet' is reinforced, not just restated.

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?

Provides clear context: 'Use only an operator-authorized wallet' and explicitly states a when-not boundary: 'This does not authorize any token transfer or approval.' It does not name an alternative tool or spell out the prerequisite call sequence, but the guidance is materially useful for selecting and using the tool.

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