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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the return-value composition (character, name, category, group) but does not disclose additional behavioral traits such as whether the random selection is truly uniform or whether repeated calls can return duplicates. Since annotations are robust, a baseline 3 is appropriate.

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 two sentences long, front-loaded with the core action and output fields, followed by a single usage sentence. No wasted words or redundant content.

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?

This is a simple tool with no parameters, a clear output schema (not shown but noted as present), and robust annotations. The description fully covers what the tool does, what it returns, and when to use it. There are no gaps requiring additional detail.

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 tool takes no parameters (schema has zero properties and 100% coverage). The description adds no parameter-specific details because none exist. Per calibration guidelines, zero-parameter tools earn a baseline of 4, and the description fulfills this by not inventing unnecessary parameter information.

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 clearly states the action ('Get a random emoji') and the resource ('emoji'), and specifies the returned fields: character, name, category, and group. It distinguishes itself from sibling tools like get_by_category or get_by_group by emphasizing randomness, making its unique purpose unmistakable.

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 provides explicit when-to-use guidance: 'Use when you need an unpredictable emoji for variety or surprise elements.' It does not explicitly contrast with deterministic alternatives like get_by_category, but the context is clear enough for most use cases, earning a 4 rather than a 5.

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