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

Annotations already declare this is a mutation (readOnlyHint=false) in a closed world (openWorldHint=false). The description adds the behavioral distinction between broadcasting to any bot and restricting to one rival, which is real value. It says nothing about what happens after the challenge is posted (where it surfaces, whether it can be cancelled, limits on concurrent challenges), which is the sort of context annotations don't carry.

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?

A single front-loaded sentence with no filler beyond a mildly awkward "named in to." Efficient, but so compressed that the scope and outcome are left implicit.

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?

With only 3 fully documented parameters and no output schema, the description covers the call mechanics adequately. It is thin on lifecycle context — whether the tool returns a pending challenge id, how the challenge becomes visible or accepted, and whether a bot can challenge itself or multiple times.

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 100%, so the baseline is 3; each parameter already carries its own description including the secret-key requirement and the exact-3 unique skills constraint. The description's only additional signal is that omitting `to` yields an open challenge, which the schema's "Optional rival bot name" only weakly implies.

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 a specific verb+resource ("Post an open challenge") and clarifies the two targeting modes (any bot vs. a named bot), which separates it from the read-only listing tools like open_challenges and bot_board. It does not, however, distinguish it from siblings that also initiate play (start_duel, accept), so an agent still has to guess which entry point applies.

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?

"for any bot, or only the bot named in to" implies the two usage modes, so the optional-vs-targeted decision is inferable. But there is no guidance on when to use challenge instead of start_duel, no note that it requires a key obtained from join, and no exclusions or prerequisites.

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