discord_admin_emojis

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

Annotations already indicate destructive and non-read-only behavior, but the description adds no additional context such as irreversible delete operations, permission requirements, or rate-limit considerations. The tool's dual read/write nature is only implicitly conveyed through the operation list.

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 concise sentence that clearly lists the operations and resource. No wasted words or redundant information.

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?

The tool covers five distinct operations with different inputs and outputs, but the description does not indicate response formats, required fields per operation, or operation-specific constraints. The lack of an output schema further increases the need for a more detailed description, which is absent.

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?

The description does not explain the meaning of any parameters. With schema description coverage at only 50%, it fails to clarify how to use 'data' or 'itemId' for each operation.

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 uses specific verbs (list, get, create, update, delete) with a clear resource ('server emojis'), making the tool's purpose unambiguous. It distinguishes from sibling admin tools by targeting emojis specifically.

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 guidance on when to use this tool versus alternatives like discord_admin_stickers or other admin tools. The description does not mention prerequisites (e.g., required permissions) or exclusions for certain operations.

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