Dice MCP Server

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

No annotations provided, so description carries full burden. It reveals stateful dependency on 'last roll' but omits critical behavioral details: whether it appends a new entry to history or modifies existing state, and what error occurs if no previous roll exists.

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?

Single sentence, eight words. Information-dense with subject (implied user), verb (Re-roll), object (last roll), and modifier (identical parameters). No waste.

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?

Adequate for a simple stateful tool but incomplete given the history-related sibling tools. Missing side-effect disclosure (history mutation behavior) and error state documentation that would be necessary for robust agent operation.

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?

Zero parameters with 100% schema coverage; baseline is 4. The description adds value by explaining why no parameters are required ('identical parameters' from previous roll), preventing confusion about the empty schema.

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 uses specific verb 'Re-roll' with clear scope 'the last roll' and explains the mechanism 'with identical parameters'. It distinctly differs from siblings roll_dice/roll_pool (new rolls) and history tools (view/clear).

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?

Implies usage context (repeating a previous action) but lacks explicit prerequisites—does not state that a previous roll must exist or warn about failure conditions if called on empty history.

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