Dice MCP Server

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

Adds temporal scope ('recent', 'this session') beyond what structured fields provide. However, with no annotations, it fails to disclose safety characteristics (read-only vs destructive) or return format.

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 is front-loaded and efficient, though given the lack of annotations and schema coverage, the brevity leaves critical gaps rather than demonstrating disciplined 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?

Minimum viable for a simple history retrieval tool. Adequate for basic selection but missing parameter documentation and output format details necessary without annotations or output schema.

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 has 0% description coverage, requiring description to compensate. The term 'recent' loosely implies limiting results, but the description fails to explain the 'limit' parameter's specific function (number of records) or its constraints.

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?

Clear verb 'Retrieve' and resource 'roll history' with scope 'this session'. Implicitly distinguishes from sibling roll/clear tools by function, though doesn't explicitly name alternatives.

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?

Provides no guidance on when to invoke versus siblings (e.g., checking history before clearing) or prerequisites. Agent must infer usage from context.

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