conversion_emoji

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

Since no annotations are provided, the description must bear the burden. It discloses that the tool returns 'detailed Unicode information, HTML entities, and UTF-8 bytes', which is moderately transparent. However, it does not mention side effects, authentication needs, or rate limits.

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 short (4 sentences) and front-loaded with actionable purpose. The last sentence about describe_tool is helpful but slightly redundant. No unnecessary information.

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 description explains the tool's purpose and output, but given two required parameters and no output schema, it lacks details on parameter constraints and usage examples. It is adequate but not fully complete.

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?

With 0% schema description coverage, the description should compensate. It hints that 'query' and 'search_type' are used for searching by name, keywords, or code points, but does not explicitly define their allowed values or format, leaving ambiguity.

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 'Emoji Unicode Lookup' and 'Search and lookup emoji by name, keywords, or Unicode code points', providing a specific verb and resource. While it distinguishes from siblings implicitly by focusing on emojis (unlike other conversion tools), it does not explicitly contrast with 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?

The description advises using describe_tool for full guidance but does not specify when to use this tool vs. siblings. No explicit context on best use cases or when not to use it.

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