app_emojis_create

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

The description confirms a creation operation ("Upload a new") consistent with readOnlyHint=false. It adds the application-scoped vs. guild-scoped distinction and specifies the return shape `{id, name, animated}`. While annotations cover safety hints, this description adds useful behavioral context beyond them.

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 compact and well-structured, using clear sections for purpose, when to use, when not to use, example, and returns. Every sentence provides essential information without fluff.

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 simple create tool with three parameters, the description covers purpose, usage scenarios, an example, and return values. The annotations handle the safety profile, so the description is complete enough for an agent to select and invoke this tool correctly.

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% with good descriptions for all three parameters. The description adds a concrete example (`{application_id:"…", name:"spark", image:"data:image/png;base64,…"}`) that illustrates parameter relationships and expected formats, slightly exceeding schema-only semantics.

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+resource combination: "Upload a new application-scoped custom emoji." It clearly distinguishes from sibling tools like `emojis_create` (guild-scoped) and other app_emojis operations (list/get/modify/delete).

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?

Explicit when-to-use guidance is provided: "Register an emoji available wherever the bot is - independent of guild." It also includes a clear when-not-to-use with a direct alternative: "Guild-only emoji → use `emojis_create`." This fully satisfies the dimension.

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