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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond them: the style applies across every signed-in device, and the response carries a subscription entitlement flag ('whether this account may wear the Lorekeeper styles'), which hints at gated styles.

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?

Two sentences with no filler, and the resource description is front-loaded ahead of the returns block. The first clause ('How your dice look...') is slightly indirect for what is fundamentally a read of a style setting.

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?

There is no output schema, yet the description documents the exact return shape (`{ style, subscribed }`) and the meaning of each field, and the annotations already cover read-only safety. Nothing an agent needs in order to call this zero-argument tool 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its words on the response contract, which is the only meaningful semantic surface here.

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 names the specific resource — the user's dice appearance in the dice bubble and roll results — which an agent can distinguish from set_dice_style and roll_dice among the siblings. It never states the verb explicitly (it is a getter), so the read semantics are inferred rather than declared.

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?

There is no explicit when-to-use or when-not-to-use guidance and no mention of the natural alternative set_dice_style for changing the style. The only implicit signal is that the tool reports current state, which an agent must infer from the returns block.

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