conflict_player_rank

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

No annotations are provided, so the description carries the full burden. It discloses that rank and contribution values retain string types, that it makes one logical GET without auto-fetching continuation pages, applies local array limits (100 rows, 256 KiB) with truncation reporting, and refuses oversized records. These are substantial behavioral details beyond the schema, though some statements appear generic (e.g., 'Array responses' may not apply to this single-object tool).

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 first sentence is concise and front-loads the purpose. However, subsequent sentences include generic caveats like 'Other declared filters are forwarded as supplied' and 'Array responses are locally limited...' that seem boilerplate and may not apply given additionalProperties:false and a single-player response. This adds noise and reduces overall conciseness.

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 simple read tool with two simple string parameters, the description covers the purpose, hints at response content (rank and contribution), and details pagination and size limits. It does not describe the exact response structure, but no output schema exists, so the description can only go so far. It adequately covers operational concerns, despite some generic statements.

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%, so the description must compensate. It only says 'by id and username', naming the parameters without explaining their meaning, format, or examples. The phrase 'Required inputs reflect tool policy as well as measured upstream requirements' is vague and does not clarify parameter semantics, leaving the agent to infer from names alone.

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?

States 'Read one player's conflict ranking by id and username' – a specific verb, resource, and parameters. It explicitly distinguishes itself from the upstream leaderboard_with_player by noting the response contains only player, not the whole leaderboard, which differentiates it from a similarly named sibling.

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 does not explicitly state when to use this tool instead of alternatives. It mentions the upstream name and the single-player scope, implying use for individual rankings, but does not name sibling tools like conflict_leaderboard or provide a decision rule. The note about forwarded filters is behavioral, not usage guidance.

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