discord_delete_invite

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

Annotations already indicate destructiveHint=true, but the description adds valuable behavioral details: 'IRREVERSIBLE (the code is freed)' and 'reason is recorded in the audit log.' No contradiction with annotations.

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 concise sentences with no wasted words. The most critical information (action, irreversibility, permissions) is front-loaded. Every sentence adds value.

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 no output schema, the description covers key aspects: purpose, permissions, side effects, and audit log. It does not mention error handling (e.g., if invite doesn't exist), but overall it is sufficient for a simple delete operation.

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 descriptions. The tool description adds extra meaning for invite_code: 'A full discord.gg/<code> URL is also accepted,' which is not in the schema description. This enhances parameter understanding.

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 'Revoke an invite by its code so it can no longer be used,' specifying the action (revoke/delete) and the resource (invite). It distinguishes from sibling tools like 'discord_create_invite' and 'discord_get_invite' by focusing on deletion.

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 permission requirements ('Requires the Manage Channels permission (or Manage Server)') and notes the irreversibility, aiding in deciding when to use. However, it does not explicitly compare with alternatives, but the context is clear enough for a dedicated delete tool.

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