List Discord emojis

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is fully covered. The description adds nothing beyond that: no mention of whether it returns only custom guild emojis versus global ones, pagination, or permission/rate-limit behavior. With annotations carrying the burden, this is adequate but adds no extra context.

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 sentence with no filler, and the key scope ('in a Discord guild') is front-loaded. It is efficient, though the terseness borders on under-specification rather than tightness.

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 single-parameter, read-only list operation with full annotations and an output schema, the description covers the minimum needed to call it. It omits useful context such as the scope of emojis returned and pagination behavior, which is a clear but modest gap.

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 description coverage is 0%, so the description must compensate for the single guildId parameter. 'in a Discord guild' only weakly ties guildId to the guild identifier and gives no format or sourcing guidance, leaving the agent to infer meaning from the parameter name and the regex pattern alone.

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 states a specific verb ('List') and resource ('emojis') scoped to a Discord guild, so an agent knows exactly what the tool returns. It does not differentiate itself from near neighbors like discord_list_stickers, but the resource noun is distinct enough to select on.

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?

There is no statement of when to use this tool versus alternatives (e.g., discord_get_guild or discord_list_stickers), and no prerequisites such as requiring the guild ID or emoji-related permissions. Usage is only implied by the name and the word 'List'.

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