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

With readOnlyHint=true and openWorldHint=true already declaring safety profile, the description adds genuine operational context the annotations cannot: the bond prerequisites and the 0.001 SOL threshold that make a balance sufficient or insufficient. It does not disclose the returned unit/format, which is a modest omission for a pure read.

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 tight sentences, front-loaded with the action, then the qualifying conditions. Dense jargon ('Trust bondedActive') is used without definition, but no sentence is pure 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?

A minimal one-parameter read with no output schema, so the description must cover both input meaning and return semantics. It covers the eligibility narrative well but leaves the argument's identity and the returned unit unexplained, which is a noticeable gap for an agent deciding what to pass and how to interpret the result.

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?

The single parameter `pubkey` has 0% schema description coverage (only a base58 regex pattern), so the description carries the burden — yet it never says whose pubkey to pass. It mentions 'payee wallet' and 'loan vault' in passing but does not tie either to the pubkey argument.

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: 'Read a Solana wallet balance on Desk.' That is unambiguous and distinguishes it from loan/gob/attestation siblings, though it never explicitly names which sibling it complements (e.g. desk_claim_job).

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 real context for when the check matters: claiming requires a bond (Trust bondedActive or a funded Desk loan), and a one-shot job with no open loan needs >0.001 SOL in the payee wallet. It stops short of an explicit 'call this before desk_claim_job' routing instruction or a when-not-to-use clause.

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