send_dice

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

With no annotations, the description carries the full behavioral burden. It does disclose the key non-obvious trait that the outcome is random and animated, but it says nothing about which chat receives the message, that chat_id defaults to the current conversation, whether the random result is returned to the caller, or any rate limiting.

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 English sentence is tight and front-loaded, but the Chinese line is a verbatim translation that adds no information for an agent reading English schema fields, so roughly half the text is redundant.

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 output schema covers return values, but for a messaging mutation with zero annotations and zero schema description coverage, the definition omits the two things an agent most needs: what chat_id does and what targeting behavior to expect by default.

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. The emoji list is merely restated (the enum already names and shows the six values), while chat_id is left completely unexplained in both schema and prose, leaving the agent to guess that it is an optional target-chat override defaulting to the current chat.

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?

"Send an animated random-value emoji" states a specific verb (send) and resource (animated emoji), and the parenthetical enumerates the six variants. It implicitly distinguishes itself from the text/media siblings by being about a self-contained random-result animation, though it never says so explicitly.

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 contains no when-to-use or when-not-to-use guidance and never references any of the twelve sibling send/edit tools. An agent must infer that this is the correct tool whenever a user wants a dice roll or spinner rather than a text or poll message.

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