discord_delete_emoji

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

With no annotations provided, the description must disclose behavioral traits. It only states 'delete' but does not mention that this is destructive and irreversible, nor that a 'confirm' parameter is required to execute. No details on permissions or error states.

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 a single sentence with no waste. However, it is overly terse and omits important behavioral and parameter details. A slightly longer description (e.g., including confirmation requirement) would be more useful without losing conciseness.

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?

Given the lack of annotations and output schema, and low parameter coverage, the description is insufficient. It does not cover return values, error handling, or the requirement to set 'confirm' to true. The tool is simple but the description still underinforms.

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 input schema has 33% description coverage (only 'confirm' described). The description adds no parameter information. It fails to explain 'guildId' and 'emojiId', nor does it clarify the role of 'confirm'. For a deletion requiring confirmation, this is a critical gap.

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 clearly states the action (delete) and the resource (custom emoji). It effectively distinguishes from sibling tools like discord_create_emoji or discord_list_emojis. However, it is essentially a restatement of the tool name, lacking additional context.

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?

No guidance on when to use this tool versus alternatives (e.g., editing or listing emojis). No information on prerequisites or conditions (e.g., required permissions like 'MANAGE_EMOJIS'). The description is silent on usage scenarios.

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