random_roll_dice

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

No annotations exist, and the description does not disclose behavioral traits such as whether it returns individual die results or just a sum, or the randomness quality. The schema parameter hint ('e.g. 2d6') is not in the description, so the description itself lacks transparency.

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 very concise at two words, but it may be too terse, sacrificing completeness for brevity. It is front-loaded but lacks structure to convey essential 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?

Given the simplicity of the tool and no output schema, the description should at least mention the return format or the standard dice notation. It fails to provide complete context, especially compared to other random tools with more detailed descriptions.

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 schema description for the parameter 'dice' includes examples ('2d6, 1d20'), providing meaning beyond the type. Since schema coverage is 100%, the description does not need to add much, but it adds nothing. Baseline 3 is appropriate.

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 'Roll dice.' clearly states the verb and resource, and it distinguishes itself from sibling tools like random_flip_coin or random_number by specifying dice rolling. However, it is very terse and could be more specific about what 'dice' means.

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?

No guidance is provided on when to use this tool versus alternatives. The description implies it is for dice rolls but does not explain when it is appropriate or when to use other random tools.

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