create_emoji

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

No annotations, so the description carries full burden. It usefully discloses the 256KB size limit and accepted input formats, but omits whether this is a privileged mutation, what happens on duplicate names, and what the response contains.

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 tight sentence with no filler; the operation, source, and size constraint are all front-loaded.

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 5-parameter mutation tool with no annotations and no output schema, the description does not cover permission requirements, role-restriction behavior, or the guild-default behavior of guildId/reason audit logging. It is adequate, not 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?

Schema coverage is 100%, so all five parameters are already documented in the schema, including the URL/base64 format for attachmentUrlOrBase64. The description adds only the 256KB constraint and nothing on new/optional params like rolesCsv.

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?

Specific verb (Upload/create) plus resource (custom emoji), and the word 'new' implicitly distinguishes it from edit_emoji and delete_emoji in the sibling set. Source formats and size cap are stated up front.

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 it (creating a new emoji from an image), but never names alternatives like edit_emoji or list_emojis, nor does it state prerequisites such as needing emoji-management permissions. Usage is inferable but not guided.

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