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

With no annotations, the description carries the full burden, and it does disclose the most important trait: 'Read only,' so the agent knows nothing is mutated. However, it says nothing about authentication expectations (own-wallet only, per the schema but unstated in the description), whether the call reverts for unregistered wallets, or what the response looks like.

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?

A single dense sentence with the scope front-loaded and no filler; the only cost is that compression into game jargon trades readability for brevity.

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?

With no output schema, the description usefully enumerates the returned categories, which is the main compensating value here. It still leaves gaps around authorization/eligibility and error behavior, but the read-only nature and the content list cover the essentials for a one-parameter read.

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%, and the wallet parameter is well documented in the schema itself ('Nothing is sent from it... read your balance and allowance and to simulate'). The description adds no meaning beyond that, so baseline 3 applies.

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 enumerates what is returned (ZENI, vehicles, claimable loot, heat, feed verification), so the resource is identifiable, but it frames the tool as 'what a wallet holds' rather than with a clear verb and never distinguishes it from near-sibling readers like `me`, `city_status`, or `get_estate`. The jargon ('Lie Lows', 'feed verification') further blurs the purpose for an agent unfamiliar with the game.

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 any alternative tool despite a large sibling set that includes several overlapping read tools. The agent must infer that this is a portfolio/status overview rather than a targeted lookup.

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