conflict_leaderboard

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

With no annotations, the description fully carries the transparency burden and does so well: it discloses the 200-row upstream vs bounded server response, single logical GET, no continuation-page fetching, 100-row/256-KiB local limits, truncation reporting, and refusal of oversized records without partial fields.

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 purpose is front-loaded and the length is tolerable, but the text has a run-on ('Makes one logical GET request Does not auto-fetch'), grammar issues ('list are'), and the vague 'Other declared filters' sentence that adds confusion. It could be trimmed without losing information.

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 one-parameter read tool with no output schema, it covers the essential runtime behaviors: data scope, truncation limits, pagination stance, and failure behavior for oversized records. Missing details are the meaning of id and explicit response shape, but these are partially covered by 'totals and prize metadata by id'.

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 schema has one bare parameter (id, string) with 0% coverage, and the description only says 'by id' plus meta notes about tool policy. It never explains what the id identifies, its expected format, or how to obtain it. The reference to 'Other declared filters' is confusing because the schema has no additional filters.

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 opens with a specific verb ('Read') and names the resource ('conflict leaderboard') along with the scope ('totals and prize metadata by id'). It does not explicitly contrast with sibling leaderboard tools, so it misses the differentiator needed for a 5.

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 explains behavioral constraints (bounded rows, no pagination, no auto-fetch) but never says when to use this tool versus conflict_player_rank, conflict_status, or player_leaderboard. Usage context is implied by the name, not stated.

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