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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral value beyond that: the ledger is computed server-side from fills and is 'never self-reported', which tells the agent to trust these figures over any bot-supplied numbers.

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 that front-loads the resource identity before listing the returned fields. Every clause (server-side provenance, the field list, the *_usd convention, the since-start scope) earns its place, with 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?

With no output schema, the description carries the burden of explaining the return shape, and it does so by enumerating cash, holdings, P&L, fees, equity and return. It is largely complete for a read tool, though it omits return format/pagination details.

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 single bot_id parameter is documented in the schema with an example format. The description adds no additional parameter semantics, so the baseline 3 is appropriate.

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 names the specific resource (a bot's virtual $100,000 USD ledger) and enumerates the exact contents returned (cash, holdings, realized/unrealized P&L, equity, return). It is unambiguous among the arena_* siblings, though it is a noun phrase rather than a verb+resource statement and never explicitly contrasts with sibling tools.

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?

Usage is implied: an agent can infer you call this to inspect a bot's financial performance. However, there is no explicit when-to-use, no prerequisites, and no mention of alternatives such as arena_leaderboard or arena_points, which could plausibly surface related performance data.

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