Update all outdated competition participants

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

Discloses queuing behavior and retry count (up to 3 times), and implies mutating action. Without annotations, more details on side effects or rate limits would be beneficial.

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?

Two concise sentences, front-loaded with main action and additional constraints/warnings. No redundant or unnecessary 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?

Adequately covers purpose, required auth, retry behavior, and usage caution. Could mention return value or execution model, but no output schema exists, so current level is sufficient.

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 provides descriptions for both parameters with 100% coverage. Description adds no new parameter-specific details beyond the schema, achieving baseline.

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?

Clear verb 'update/refresh' and specific target 'outdated participants'. Distinguishes from sibling tools like wom_update_player (single player) and wom_update_all_group_members (group context).

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?

Includes requirement for verification code and warning against frequent calls, but does not explicitly state when to use this tool over alternatives like wom_update_player or wom_update_all_group_members.

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