get_roll_history

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

Annotations already indicate a read-only, non-destructive operation. The description adds valuable context that hidden rolls only show '结果保密' (result confidential), disclosing a key behavioral trait not evident from annotations.

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 brief, front-loaded with the primary purpose, and then uses concise examples to demonstrate usage. Every sentence serves a purpose with no redundancy.

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 covers core functionality, hidden-roll behavior, and usage patterns. It omits output format, but no output schema is provided, and the examples sufficiently guide the agent for common query needs.

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 description compensates by illustrating offset usage (limit=10, offset=10), clarifying pagination. The tag example reinforces filtering. It does not cover locale, but the enum in schema handles that.

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 '查询掷骰历史' (query dice roll history), a specific verb+resource combination. It distinguishes from sibling roll tools, and the note about hidden rolls adds important scope.

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 provides concrete usage examples (limit, tag, pagination) and implies that hidden rolls are not fully visible, guiding agents to not expect reveal functionality here. However, it does not explicitly name alternative tools like reveal_hidden_roll for full results.

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