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

Annotations already provide readOnlyHint=true and destructiveHint=false, lowering the bar for behavioral disclosure. The description adds genuine value beyond this with the security guarantee "AgentLot never asks for a seed phrase/private key," which meaningfully shapes agent behavior by ruling out a harmful interaction pattern. The description is consistent with the read-only annotation and adds a distinctive trust boundary not captured by the structured fields.

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 short sentences with zero waste. The primary purpose is front-loaded in the first sentence, and the second sentence delivers a high-value security guarantee. Every word earns its place for a tool this simple.

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 tool with zero required parameters, full schema coverage, and read-only annotations, the description is nearly complete: it states the outcome, the security boundary, and the schema documents the only optional parameter. The main missing piece is positioning against the dense cluster of wallet/payment siblings, and since there is no output schema, a slightly richer hint about the returned shape would improve completeness, but the low complexity keeps this from being a major deficiency.

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 100%, so the baseline of 3 applies. The single api_key parameter is well-documented in the schema (optional, when to use it, preferred alternative), and the description doesn't need to repeat this. The description adds no parameter-level detail itself, but none is required given the schema's completeness.

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 states a specific verb and resource: "Return user-controlled wallet options for AI agents." The qualifier "user-controlled" adds meaningful scope beyond just 'wallet options,' and the second sentence reinforces what the tool is not (a credential-harvesting flow). However, it does not differentiate from closely related siblings in the same space (list_my_wallets, get_payout_options, get_payout_methods, connect_public_wallet), so an agent cannot tell them apart from the description alone.

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?

There is no guidance on when to use this tool versus alternatives. With several overlapping wallet/payment siblings listed (list_my_wallets, get_payout_options, get_payout_methods), the absence of any selection criteria or exclusionary statement is a significant gap. The only usage-related hint ('Prefer connector-level Bearer auth for persistent integrations') is authentication guidance for the optional api_key parameter, not tool-selection guidance.

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