player_richlist_ranking

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

No annotations are present, so the description carries full burden. It discloses one logical GET request, no auto-fetch continuation pages, local truncation at 100 rows/256 KiB with reporting, and refusal of oversized records without partial fields. This is unusually specific behavioral detail.

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 front-loaded with purpose and requirements, then packs behavioral caveats into the remaining sentences. It is dense rather than padded, though several edge-case sentences could be tightened.

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 two-parameter read-only tool with no output schema, the description covers invocation requirements, upstream behavior, pagination, and truncation. It is mostly complete; only return formatting and potential error cases beyond oversized records are left unspecified.

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 description only states that both parameters are required and explains why player is needed. It doesn't define accepted token_type values or player identifier format, but the names plus the 'token rank and balance' context are self-explanatory enough for basic invocation.

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?

Description opens with a specific verb and resource: 'Read one player's token rank and balance as the upstream reports them.' This clearly distinguishes it from the sibling player_richlist by emphasizing single-player scope, and avoids tautology.

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?

It states that token_type and player are required and explains the upstream consequence of omitting player: 'without player the upstream returned only token_type, which is not an account ranking.' This gives clear usage context, though it does not explicitly name an alternative tool or when-not conditions.

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