discord_delete_invite

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

The description adds meaningful behavioral detail beyond the annotations: the operation is IRREVERSIBLE, the code is freed, it requires Manage Channels (or Manage Server) permission, and the reason is recorded in the audit log. This goes well beyond the destructiveHint and idempotentHint already provided.

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?

Three short sentences, each carrying essential information: the primary action, the irreversibility warning, and the permission/logging context. No filler, no repetition of schema details, and key warnings are 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?

The description is complete for a simple two-parameter destructive tool. It covers purpose, permission requirements, irreversibility, audit logging, and the parameter format is already fully documented in the schema. No output schema exists, but a successful delete response is not essential for an agent to invoke this 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?

The input schema already has full (100%) coverage of both parameters, including the fact that reason is optional and recorded in the audit log. The description adds little parameter-specific meaning beyond referring to 'code' and mentioning the audit log, so the schema carries the load as expected.

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 action (revoke), the exact resource (an invite identified by its code), and the direct consequence (it can no longer be used). This clearly distinguishes it from sibling tools like discord_create_invite, discord_get_invite, and discord_list_invites.

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 provides clear context for when to use the tool: revoking an invite code that should no longer work. It also states the required permission, which helps the agent decide whether it can perform the operation. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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