Reroll the shop

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds a meaningful side-effect disclosure: '商店索引在刷新后全部失效' (all shop indices become invalid after refresh), which is behavioral context beyond annotations. No contradiction detected.

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?

The description is extremely concise—one short sentence with two clauses—and every part earns its place: availability condition and invalidation side-effect. It is front-loaded and free of 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?

This is a simple tool with one parameter and no output schema. The description covers the critical constraints (SHOP-only usage and index invalidation) and is adequate for an agent to use it correctly. A slight additional statement about what rerolling actually does (e.g., refreshes items) would make it fully complete, but the title provides that.

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?

The single parameter expected_state_token is fully documented in the schema (100% coverage), so the description does not need to add parameter details. The baseline of 3 applies because the schema carries the burden and the description does not contradict or add extra parameter 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?

The title 'Reroll the shop' clearly identifies the action and resource, distinguishing it from siblings like buy/discard/sell. The description adds availability context but does not explicitly restate the core purpose, relying on the title for that.

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?

The description states '仅 SHOP 可用' (only available in SHOP), providing clear context for when the tool is applicable. It does not mention alternatives or explicit exclusions, but the condition is a useful usage guideline.

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