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

With no annotations, the description must carry the full burden of behavioral disclosure. It states the data returned but does not say whether the call is read-only, whether it requires permissions, or what side effects (if any) occur. This is a significant gap for a balance/claimability query.

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?

The description is a single, front-loaded sentence with no wasted words. It is concise and focused, though its brevity contributes to gaps in other dimensions rather than being a structural flaw here.

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 simple one-parameter read tool, the description should at least explain the wallet input and confirm the operation is non-mutating. With no annotations, no output schema, and no parameter documentation, the definition is insufficient for an agent to invoke it confidently.

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 schema has one required parameter ('wallet') with 0% description coverage, and the description never mentions the parameter or explains what value to supply. It refers to 'this caller' but does not connect that to the wallet argument, adding no meaning beyond the 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?

The description specifies what the tool returns: what the platform owes the caller per token in USDC and what can be claimed now. It is clear about the resource and scope, though it lacks an explicit retrieval verb and does not distinguish itself from siblings like prepare_claim_transaction or get_fomo_bonus.

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?

No guidance is given on when to use this tool versus alternatives such as prepare_claim_transaction or other get_* tools. The implication that it is useful before claiming is not stated, leaving usage context to inference.

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