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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds real substance beyond them: the winner is drawn server-side with a cryptographically secure RNG, weights are honored, duplicates are removed, and an animated wheel is rendered in chat. It also instructs the agent to report the winner from the result text rather than inventing one, which is valuable behavioral guidance. Minor gap: no mention of latency, rate limits, or what happens on malformed input.

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 purposeful sentences with the core action front-loaded and the exclusion last, which is the right ordering. The long tracking URL with UTM parameters is the only mildly wasteful element, though it is functional rather than filler.

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 read-only, non-idempotent randomness tool, the description covers inputs, the drawing mechanism, weighting, rendering, and how to consume the result. Since an output schema exists, it does not need to enumerate return fields, so nothing an agent needs in order to call it correctly is missing.

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 schema already explains title, entries, and the 1–10 weight scale and ordering. The description only restates that weights are optional and respected, adding no syntax or edge-case detail beyond the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

Opens with a concrete verb+resource ("Spin a random picker wheel") and enumerates the decision categories it covers (names, places to eat, teams, giveaway winners, yes/no). It is unmistakably distinct from the siblings create_wheel_link and list_wheel_templates, which build or list wheels rather than draw a winner.

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 an explicit trigger list ("pick, draw, choose randomly, decide for them, or spin a wheel") and an explicit exclusion with a redirect: Secret Santa draws should go to the external URL instead. Both the when and the when-not are stated rather than left to inference.

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