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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-lookup profile is covered. The description adds the balance threshold, which is real behavioral value, but says nothing about how the check resolves (RPC lookup, caching, failure modes) beyond the threshold.

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?

One sentence front-loads the action, the threshold, and the fallback. There is no 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 trivial single-param read-only check, the description plus annotations cover what an agent needs to call it correctly: purpose, threshold, and the loan alternative. Without an output schema it does not say what the result looks like, which is the main remaining 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?

Only one parameter, and the schema gives its regex pattern but no prose. The description implies pubkey is the wallet address to check, but adds no further semantics such as accepted address forms or what invalid input does. Baseline 3 for a single-param tool with an undocumented schema.

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 (Check) and resource (a Solana wallet as a Desk claim payee), and names the exact threshold condition. It is distinguishable from siblings like desk_loan_status or desk_request_loan because it validates payee eligibility rather than managing a loan.

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?

Clear context: use before setting a claim payee, with a concrete pass criterion (> 0.001 SOL) and an escape hatch (use a Desk loan). It does not explicitly name alternative siblings to use instead, so it stops short of a 5.

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