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

No annotations are provided, so the description must carry the behavioral burden — and it does thoroughly: 'Consumes exactly one spin (NOT free to repeat)', 'earned from check-ins/deposits', 'credits shopping balance (not withdrawable)', 'Requires api_key'. All side effects and preconditions are disclosed in plain language.

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?

Information is front-loaded — the core action and outcome come first, followed by the consumption warning possession. Caps-labeling (PREREQUISITE, WHEN TO USE, PREFER INSTEAD) makes it scannable. Slight redundancy: the closing Vietnamese sentence restates already-covered content (one spin per call), which adds length without new 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?

Covers purpose, side effect (consumes a spin), source of spins, destination of winnings, auth requirement, and sibling routing. With no output schema, it could additionally note error/edge-case behavior (e.g., what happens when the user has zero spins), but as-is it gives an agent everything needed to decide and execute the call.

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% for the single parameter (api_key is described as 'Your shop account API key.' in the schema). The description only restates 'Requires api_key' without adding format or origin details, so it adds little beyond the schema. Baseline 3 applies.

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?

The opening clause uses a specific verb and resource ('Spin the lucky wheel once') and states the output ('return the prize won + new balance'). The action is unmistakable and distinct from siblings like daily_checkin or gamefi_status, which appear in the same inventory.

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?

Explicit WHEN TO USE ('user has spins and wants to use one') and PREFER INSTEAD (`daily_checkin` to earn a spin, `gamefi_status` to check spin count) sections name the exact alternatives and the conditions that select them. An agent gets full routing guidance.

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