player_burn_event_full_leaderboard

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

There are no annotations, so the description carries the full disclosure burden, and it does so exceptionally well. It reveals the bounded response, ignored paging, local 100-row/256 KiB limits, truncation reporting, oversized-record refusal, string wire types, and lack of auto-fetching.

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 dense but each sentence earns its place by disclosing a distinct behavioral fact. It is slightly verbose and has minor grammatical awkwardness, but it is well organized and front-loads the core purpose before edge behaviors.

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 tool with no annotations, no output schema, and no parameters, this description is remarkably complete. It covers what data is returned, the response size limits, truncation behavior, refusal of oversized records, wire types, and confirmation that pagination/continuation will not happen automatically.

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 input schema has zero propertiesigned, so there is little for the description to enrich. It mentions that filters are forwarded and that required inputs reflect policy, but since no parameters are declared, this is not misleading; the baseline for no parameters 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 names a specific verb ('Read'), a specific resource ('upstream full burn-event ranking route'), and the expected content ('rank/player/points rows'). It immediately clarifies that the server returns only a bounded leading portion rather than the full ranking, which distinguishes it from what the name might otherwise imply.

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?

The description provides strong context about what not to expect: limit/offset are ineffective, paging is not exposed, and only one logical GET is made. However, it never explicitly says when to prefer this tool over sibling burn-event leaderboard tools or when not to use it.

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