reveal_hidden_roll

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

The annotations do not indicate read-only (readOnlyHint=false), and the description says 'unlock', implying a state change. Yet it does not disclose whether the reveal is permanent, whether it affects all players, or any authorization requirements. The description carries a low burden but still lacks behavioral detail.

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: two short sentences plus two examples. It leads with the primary purpose and includes only necessary details, with no redundant 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?

The description states the return value ('完整掷骰明细') but does not detail output structure or edge cases. Given no output schema, more detail could be expected, but for a simple reveal tool, it is minimally complete.

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 67%, and the schema already describes roll_id and reason. The description adds useful examples of roll_id formats (h7, #h12) and reason usage, but does not explain locale. The baseline of 3 is appropriate since the schema does most of the work.

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 description clearly states the tool's function: unlocking and viewing hidden dice roll results and returning complete roll details. It uses a specific verb-resource pair ('解锁查看' / '暗骰结果') and is easily distinguished from sibling rolling 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?

The description implies usage for hidden rolls and provides examples, making the context clear. However, it does not explicitly state when not to use it (e.g., for normal rolls), but sibling tools like roll_dice provide sufficient contrast.

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