Roll Dice

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It does not mention that the result is random, that it is a safe non-mutating operation, or any other behavioral trait beyond the literal act of rolling. This is a significant gap for a tool whose entire purpose is random generation.

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 a single concise sentence with no waste. The core action is front-loaded. It is appropriately sized for a tool with only two parameters, though it could have been slightly more informative without losing conciseness.

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 tool with two parameters fully documented in the schema, the description is reasonably complete. However, the lack of any mention of randomness or return behavior (even though no output schema is provided) leaves a small but notable gap. An agent might not know the outcome is random without prior knowledge.

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 100%, so the schema already documents both parameters (count and sides) with defaults, minimums, and maximums. The description adds no semantic meaning beyond what the schema provides, which meets the baseline of 3.

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 states exactly what the tool does: 'Roll one or more dice with a given number of sides'. It uses a specific verb (roll) and resource (dice), and clearly distinguishes from the sibling flip_coin, since dice and coins are different objects.

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 on when to use this tool versus the sibling flip_coin. The context implies dice vs coin, but the description does not explicitly state that this is for dice and flip_coin is for coins, nor does it mention any exclusions or alternative conditions.

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