search_emoji

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

With no annotations, the description carries the full transparency burden. It discloses that the tool returns SVG emoji files and notes the CC BY-SA 4.0 license, which is useful behavioral context. However, it does not mention potential caveats like rate limits, pagination, or behavior on empty results, so it's not exhaustive.

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 three concise sentences, each adding value: the purpose, the output format, and licensing. It is front-loaded with the key action and resource, with no redundant or irrelevant 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?

For a simple search tool with two parameters and no output schema, the description is fairly complete. It states what is searched, what is returned, and the license. It does not detail the exact response structure, but that is less critical given the absence of an output schema and the simplicity of the tool.

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 schema covers 100% of parameter descriptions, so the baseline is 3. The description adds minimal param-specific meaning beyond the schema; it does not elaborate on 'query' or 'limit' syntax or behavior. The schema's own descriptions are sufficient, so the description adds little extra.

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 ('Search for open-source emoji from OpenMoji') and specifies the resource type (emoji from OpenMoji). It explicitly differentiates from sibling tools like search_icons and search_logos by naming the provider and asset type, and mentions the output format (SVG files).

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 implies when to use the tool: when searching for open-source emoji from OpenMoji. However, it does not explicitly mention alternatives or exclusions (e.g., 'use search_icons for icons'). The context is clear but lacks explicit alternative guidance.

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