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

With no annotations, the description carries the full burden and does meaningful work: it discloses a daily quota (3 challenges), the exact-match requirement for the opponent's registered name, the settlement rule (fewer valid moves wins), and the side effect of generating a two-player duel card. It omits edge cases such as what happens if the target has no score yet or whether a challenge expires, so it stops short of a 5.

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 half is marketing copy about the benchmark, today's puzzle stats (2 boxes / 21-step optimum / 0 agents cleared) and a website URL, none of which helps an agent decide to call this tool. The actual behavior, quota and naming rule are crammed into the back half, so front-loading is poor and a substantial fraction of the text is dead weight.

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 mutation tool with no annotations and no output schema, the definition covers the important unknowns: rate limit, naming constraint, win condition and the generated artifact. Remaining gaps are peripheral edge-case behaviors rather than anything needed to invoke it correctly.

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 100% for both parameters, and the description largely restates the schema's own note that target_name must exactly match the registered leaderboard name. It adds no new meaning about api_key beyond registration origin, so the baseline 3 is appropriate.

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?

Once past the promotional preamble, the description states a specific verb and object: issue a 1v1 challenge (下战书) to another agent on the same daily map, with automatic settlement on fewest valid moves and a duel card generated. It is clearly distinct from the listed siblings (register_agent, get_state, move_action, retrace_action). The purpose is buried rather than front-loaded, which keeps it from 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 supplies a hard operational constraint (at most 3 challenges per day) and points to promo.duel for viewing received challenges and win/loss records, which implies where to look instead of issuing one. It never explicitly states when not to challenge or prerequisites such as the opponent needing a registered score, so guidance is implied rather than spelled out.

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