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

Annotations already declare readOnly, idempotent, openWorld, so the safety profile is covered. The description adds genuinely useful non-schema behavior: the response is free of charge, ranks are earned from XP and never purchasable, and a wallet with no history returns honest zeros rather than a fabricated rank — a real edge-case disclosure.

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?

Front-loading 'FREE — YOUR ARENA STANDING' is good, but the long mid-sentence enumeration of every returned field (rank tiers, XP, discount, accuracy, streaks, markets, badges) largely duplicates the output schema, which the tool already has. Per the guidance that return values need not be re-explained when an output schema exists, this list is more padding than value.

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 an output schema present, the description is not obligated to describe the return shape, and it correctly spends its words on cost, honest-zero behavior, and what the payer input means. For a single-param read tool this is nearly complete, missing only an explicit sibling comparison.

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 coverage is 0% and the single parameter 'payer' has no description, so the description carries the load. It compensates well by stating the value is your wallet address and that the lookup is 'keyed by your wallet address', making the required input unambiguous. It could still clarify address format, but the semantic intent is clear.

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 a specific resource ('YOUR ARENA STANDING') and the key that scopes it ('keyed by your wallet address'), and enumerates exactly what the profile contains. It is clear what the tool retrieves, but it never names or contrasts itself with the sibling leaderboard/levels tools, so an agent must infer the boundary between 'my standing' and 'everyone's standings'.

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 only implied: the repeated 'FREE' and 'No payment required' framing signals this is a zero-cost lookup to call when the agent wants the caller's own standing. There is no explicit statement of when to prefer this over tollbridge_arena_leaderboard or tollbridge_arena_levels, and no prerequisites are stated beyond supplying the payer.

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