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

With no annotations, the description must carry the behavioral load, and it does add real substance: cryptographic security guarantees, the weighting rule ('an item listed twice has twice the chance unless dedupe=true'), and the fairness motivation. It omits return format, pagination/limits, and what happens when the item count is not divisible by the requested team count despite promising 'even teams'.

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?

Three sentences, front-loaded with the core capability, then use cases, then the one non-obvious caveat. No filler and no restatement of the tool name or schema fields.

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 5-parameter tool with no annotations and no output schema, the description covers purpose, use cases, fairness mechanism and weighting behavior well. The gap is that it never describes what comes back (e.g. winners list vs. shuffled array vs. team groupings) and glosses over uneven-team edge cases, which an agent must infer.

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%, so the baseline is 3, but the description adds semantics the schema does not state: that duplicates act as weights and that dedupe=true overrides that weighting. It also implicitly frames mode selection through the three named operations, tying 'pick', 'shuffle' and 'teams' to concrete intents.

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 three concrete operations (pick winners, shuffle, split into teams) against a named resource ('a list'), with the qualifier 'fairly' and the mechanism 'cryptographically secure generator'. This clearly separates it from the random_number sibling, which produces values rather than selecting from user-supplied items.

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?

Gives concrete use scenarios ('giveaways, raffles, who goes first, random order or team splits') and even explains why the agent needs it ('you cannot choose fairly at random yourself'). It does not, however, name or exclude any alternative tool, so the agent gets context but no explicit routing rule.

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