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

Goes well beyond the annotations: discloses that entries are closed (the concrete destructive effect behind destructiveHint), that the seed is published on the public page for verification, that a minimum of one entry is required, and that reruns are safe because results are final — matching idempotentHint with a plain-language reason.

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?

Five short sentences, front-loaded with the trigger condition, then mechanics, then the idempotency guarantee and exclusions — no filler or repetition.

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?

An output schema exists so return values need not be explained; the description instead covers the preconditions, side effects, verifiability, and repeat-run behavior an agent needs before invoking a destructive, one-way operation.

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?

Only one parameter and schema coverage is 100%, so the schema already documents manage_url with an example format. The description only restates that it takes the private organizer link, adding no new syntax or constraints.

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 and resource ('pick the winners of a draw'), names the sibling that creates the draw it operates on, and distinguishes itself from add_draw_entries and show_draw_results by ruling out adding names and redrawing.

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?

Explicitly conditions use on the organizer being ready, references the create_prize_draw prerequisite, and states exclusions ('does not add or remove names and does not redraw'), which routes the agent away from the entry and results tools.

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