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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the write nature is already known. The description adds genuinely non-redundant behavior: the draw is created immediately and cannot be modified from this server afterwards, plus a note that the first participant becomes organizer and that the result carries a draw id and share code.

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?

Front-loads the core purpose, then requirements, then lifecycle constraint, then the two follow-up paths. Every sentence carries information, though the long brand/alias enumeration in the opening does add some visual 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?

Given an output schema exists, the description need not detail return values, yet it briefly previews the draw id and share code. Combined with the irreversibility warning, required-input summary, and sibling routing, an agent has everything needed to call 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 description coverage is 100%, so the baseline is 3. The description reinforces which arguments are required versus optional, but most of that detail (organizer ordering, minItems 3, locale/brand mapping, optional budget and message) is already spelled out in the schema descriptions, so it adds little new meaning.

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 ("Creates a Secret Santa / gift exchange draw") with concrete mechanics (random pairing, exclusion rules honored). It is immediately distinguishable from the invitation-focused siblings, which are not creation tools.

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 separates required inputs (date, 3+ participants) from optional ones and explains the follow-up routing to send_invitations_email or get_group_share_message. It does not name a condition under which you would choose a different creation path, but none exists, so the gap is minor.

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