conflict_players

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

With no annotations, the description carries the full behavioral burden and does substantial work: it discloses a single logical GET request, no automatic continuation-page fetching, a 100-row/256 KiB local limit, truncation reporting, refusal of oversized records, and filter passthrough caveats. Some behavioral statements remain unclear, and auth or error semantics are absent, but the disclosed operational constraints are genuinely useful.

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 repeats the same filter-passthrough warning twice and contains punctuation issues like 'request Does' without a period. Useful details are present, but they are buried under redundant disclaimers and vague meta-commentary, so the structure does not make every sentence earn its place.

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?

The description covers operational limits and pagination well for a read endpoint, but with no output schema and no annotations, it must also clarify parameters and return shape. It leaves the required `player` parameter undefined and does not describe the response format beyond threshold and truncation metadata, so an agent cannot confidently construct a correct call.

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 description coverage is 0% with 9 parameters, so the description must compensate heavily. It only clarifies that id/conflict are selectors and vaguely states that other filters are forwarded without implied effectiveness. The required `player` parameter and most other parameters (`mode`, `uids`, `order_by`, `non_zero_rp`, `airdrop_data`) remain essentially undefined.

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 clearly states a specific read operation: reading a player's conflict reward-point record and reward_point_threshold, and identifies id/conflict as selector inputs. However, it does not distinguish this tool from related conflict siblings and the phrase 'Both aliases selected the captured current conflict' is grammatically confusing.

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?

There is no guidance on when to use this tool versus alternatives such as conflict_player_rank or conflict_leaderboard. The description only warns that non-primary filters are forwarded without presumed effectiveness; it offers no preconditions, exclusions, or decision rules.

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