app_emojis_delete

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

Beyond annotations, the description discloses that deletion is irreversible, requires __confirm:true, depends on MCP_DRY_RUN=false, and returns the deleted object. This gives the agent the operational safety context needed to invoke destructive behavior correctly.

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 well-structured with bolded section headers and bullet points, making it scannable. Every sentence serves a purpose, and the critical destructive warning is 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 destructive 3-parameter tool with output schema, annotations, and sibling context, the description covers purpose, usage boundaries, confirmation flow, and return shape. Nothing essential is missing for an agent to call it 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 description coverage is 100%, so the schema already documents all parameters. The description adds useful context about omitting application_id to target the authenticated bot application and reiterates the confirmation requirement, but it does not need to add much more.

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?

Description opens with a specific verb and resource: 'Delete an application emoji.' It distinguishes itself from the sibling tool emojis_delete by explicitly scoping to application emoji versus guild emoji. The destructive nature is highlighted immediately.

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?

Provides explicit 'When to use' and 'When NOT to use' sections. Names the alternative tool emojis_delete for guild emoji, which removes ambiguity for an agent selecting the correct endpoint.

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