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

Annotations already declare the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description is not required to restate that. It does add useful substance by naming the three data categories returned, but says nothing about auth expectations, visibility scope ('your' implies agent-scoped), or freshness of balances.

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-loaded with the verb and the returned domains, with no filler. It is arguably too terse for the ambiguity it leaves, but nothing is wasted.

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 no-argument read tool this roughly suffices, and the description usefully substitutes for the absent output schema by enumerating the three result areas. It stops short of clarifying the optional agent_key, the scope of 'your', or any error/empty states, so it is adequate rather than complete.

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 0% and the description supplies no information about the sole agent_key parameter — what it identifies, whether it is required, or how it is obtained. With the single parameter fully undocumented in both places, the description fails to compensate.

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?

Names a specific verb ('Read') plus three concrete data domains (royalty balance, frozen payment wallet, payout states), so an agent knows exactly what this tool surfaces. It does not, however, name or contrast itself with the nearest financial siblings such as speedbot_exchange_settle or speedbot_exchange_wallet_message.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the ~15 earnings/wallet-adjacent siblings. The agent must infer invocation conditions entirely from the resource names.

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