list_emojis

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

With no annotations provided, the description carries the behavioral disclosure burden. It adds valuable context by specifying the return format ('flat JSON object mapping each emoji name') and the data source ('CDN image URL on github.githubassets.com'). It doesn't discuss authentication or rate limits, but for a simple read-only list operation, the disclosed behavior is adequate.

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 concise and front-loaded with the core purpose, followed by a precise return-type clarification, practical use cases, and a documentation link. Every sentence earns its place, with no wasteful filler.

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 low complexity (zero params, no output schema), the description fully covers what the agent needs: the response format, example keys, and the URL domain. It also includes use cases and a docs reference, making it complete for this simple endpoint.

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?

This tool has zero parameters, so the baseline is 4. The description adds no parameter-specific detail because none is needed; it instead focuses on the output shape, which is more relevant for this parameterless API.

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 opens with a specific verb and resource: 'List all emoji names available to use on GitHub, with their corresponding image URLs.' It clearly distinguishes this tool from sibling tools by focusing exclusively on emoji data, and the scope is unambiguous.

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?

It provides clear context for when to use the tool: 'Useful for populating emoji pickers, validating emoji names, or fetching emoji images.' It does not explicitly mention when not to use it or alternatives, but given the tool's unique function among siblings, the context is sufficient.

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