github_emojis

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

No annotations are provided, so the description carries the full burden. It does disclose the return content ('with their image URLs'), which tells the agent this is a read-only enumeration rather than a lookup by name, but it says nothing about result size, whether it is static/cached, or whether an image URL is always present.

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?

A single front-loaded sentence with no filler. Every word earns its place: verb, resource, scope (all), and payload (image URLs).

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?

No output schema exists, so the description should hint at the return shape, and 'with their image URLs' partially does. For a zero-parameter, zero-risk enumeration this is close to sufficient; a brief note on result size or output key names would make it 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?

The tool takes zero parameters, so the schema has no semantics to explain and the baseline is 4. Nothing in the description conflicts with the empty parameter object.

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?

States a specific verb (List) and resource (GitHub emojis) plus what comes back (image URLs). It is distinguishable in substance from siblings like emoji_lookup or emojihub_* because it names GitHub specifically, but it never explicitly contrasts itself with those siblings.

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?

No when-to-use, when-not-to-use, or alternative named. With three other emoji tools in the sibling list (emoji_lookup, emojihub_by_category, emojihub_random), an agent gets no signal about which to pick for a given emoji need.

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