discord_delete_invite

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions the conditional confirmation requirement ('Requires confirm=true when confirmation is enabled'), which is a useful behavioral trait. However, it does not mention the irreversible nature of deletion, permission prerequisites, or what occurs if confirm is omitted when required. It adds only partial behavioral context.

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?

Two concise sentences with no wasted words. The primary action is front-loaded in the first sentence, and the conditional confirm requirement is a short, separate second sentence. The structure is direct and easy to parse.

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 4 parameters and no annotations, the description is incomplete. It explains the core action and one condition but ignores reason and guild_id entirely. Although an output schema exists (so return values need not be described), the missing parameter semantics and lack of behavioral detail (e.g., irreversible deletion) leave the tool underspecified for correct invocation.

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 0%, so the description must compensate. It implicitly covers invite_code ('by code') and confirm (the requirement), but it does not explain reason or guild_id at all. Neither the schema nor the description clarifies their purpose, leaving two parameters semantically undefined for an agent.

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 an invite') and the identifying attribute ('by code'). It distinguishes this delete tool from sibling delete tools like discord_delete_channel or discord_delete_role by specifying the resource (invite).

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 a clear context for when to use this tool (when deleting an invite) but does not explicitly name alternatives or exclusion conditions. The confirm requirement is a parameter usage note, not a tool-selection guideline. There is no explicit when-not or comparison to other delete tools, but the context is straightforward.

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