conversion_emoji

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

Annotations already provide readOnlyHint, destructiveHint, and idempotentHint. The description adds value by stating it's a 'pure client-style compute over a built-in ~170-emoji database (no network, no external API); read-only and non-destructive' and mentions rate limits of 60 requests per minute for anonymous callers. This provides useful behavioral context beyond the annotations.

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 well-structured with multiple sentences, each adding value. It front-loads the main purpose and then provides usage guidelines, behavioral notes, and parameter details. Slightly verbose but no wasted words; could be a bit more concise but still effective.

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?

Given the tool's moderate complexity and the presence of an output schema, the description covers all necessary aspects: purpose, usage, behavior (including database size and rate limits), and parameter semantics. No gaps are apparent.

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 coverage is 100% with detailed descriptions for both parameters (query and search_type). The description adds a brief summary of search types but does not significantly enhance the meaning beyond the schema. Baseline 3 is appropriate since the schema already does the heavy lifting.

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 tool's purpose: to look up emoji by glyph, name, keyword, category, or Unicode code point and return Unicode metadata plus HTML entities. It uses specific verbs like 'look up' and 'return', and distinguishes itself from sibling tools like conversion/emoji/random, encoding/unicode, and encoding/html-entities. This makes the purpose very 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?

The description explicitly tells when to use this tool: 'when you have one search term and want full Unicode/HTML detail for matching emoji'. It also provides clear alternatives: 'use conversion/emoji/random instead to sample random emoji without a query, and encoding/unicode or encoding/html-entities for escaping arbitrary text rather than looking up emoji'. This is excellent guidance.

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