Dice Roll

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals secret-roll visibility, the 2.1s minimum interval, the 30/min WebSocket rate limit, and that queuing does not raise an error. It does not cover failure modes or permission requirements, but the most important side effects are disclosed.

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 deliver purpose, syntax, secrecy behavior, and rate limiting with no filler. Critical call-shaping information is front-loaded, and every phrase earns its place.

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?

For a simple two-parameter tool, the description covers expression syntax, secret rolling, and rate limiting. Since an output schema exists, return-value documentation is not required; the only notable gap is behavior on invalid expressions, which is minor.

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 description coverage is 0%, so the description must compensate. It explains the expression parameter through examples and clarifies that is_secret=true means only the DM can see the roll. It does not formalize the full expression grammar, but an agent can construct valid calls from the provided examples.

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 indicates the tool performs dice rolls by giving concrete expression formats such as 1d20+5, 2d6, and 4d6kh3. It does not use an explicit verb like 'roll', and it does not differentiate itself from siblings by name, but the examples and tool name make the purpose unmistakable.

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 actionable usage context: is_secret=true is for hidden rolls visible only to the DM, and there is a client-side minimum interval of 2.1s with WS rate limiting. It does not explicitly state when not to use the tool or name alternatives, but no sibling tool overlaps with dice rolling.

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