discord_list_emojis

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' adds nothing. The one genuinely non-obvious disclosure is that an empty roles list means the emoji is usable by everyone, which is valuable semantic context not available in structured fields. Missing are permission prerequisites (e.g. Manage Expressions) and any note on volume or ordering, and the field enumeration largely duplicates the output schema.

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?

One front-loaded sentence covering scope, output fields, and the roles semantic; nothing is buried. The trailing 'Read-only.' is pure redundancy against readOnlyHint and could be cut.

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?

With a 1-param schema, full coverage, annotations carrying safety, and an output schema documenting the return shape, the definition covers what an agent needs to call it correctly. Only the permission prerequisite for listing role-restricted emoji is unstated.

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 coverage is 100% and the single guild_id parameter is fully documented with a snowflake pattern in the schema itself. The description's 'in a server' merely echoes that parameter without adding format or validation detail, so baseline 3 applies.

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 and resource ('List every custom emoji in a server') and enumerates the returned attributes, which cleanly separates it from the write-side siblings (discord_create_emoji, discord_edit_emoji, discord_delete_emoji) and from discord_list_stickers. An agent can identify the tool without opening the schema.

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 read-only list framing implies usage, but there is no explicit 'use this when you need emoji IDs before editing/deleting' guidance and no named alternative or exclusion. The agent must infer that this is the discovery step preceding discord_edit_emoji / discord_delete_emoji.

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