sendDice

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

With no annotations, the description carries the transparency burden. It discloses the core behavior (animated emoji, random value) and the success return value (sent Message). It does not go further to mention failure conditions, permission requirements, or that the random outcome is server-determined, so it is adequate but not rich.

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 short sentences convey the action, the behavioral highlight, the return value, and the supported emoji set. The most important facts are front-loaded and no sentence is wasted.

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?

The schema documents all 12 parameters, and the description provides the missing behavioral context (random value, returned Message, allowed emoji). It is slightly incomplete in that it does not distinguish itself from sibling send tools or mention prerequisites, but those are covered enough for a calling agent.

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 input schema has 100% parameter coverage, so the description does not need to restate parameter meanings. The description adds no real parameter semantics beyond noting the supported emoji, and the schema already covers that for the emoji parameter, so a baseline score 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 begins with a specific action and object: 'Send an animated emoji that will display a random value,' which clearly distinguishes it from ordinary sendSticker/sendAnimation operations. It also lists the supported emoji, leaving no ambiguity about what resource the tool acts on.

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 supported-emoji list and the notion of a random result imply the intended use case (casino/sports game emoji), but the description does not explicitly say when to prefer sendDice over sendAnimation, sendSticker, or sendGame. There is no exclusion or alternative routing, so the guidance is only implied.

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