discord_delete_invite

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

The description lacks behavioral details. It says 'Revoke' which implies a destructive action but does not mention permissions, side effects, or irreversibility. The 'confirm' parameter in the schema partially addresses this, but the description itself does not.

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 extremely concise at 4 words, but it is too minimal to be informative. While front-loaded, it lacks structure and could include more detail 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 destructive nature of the tool and the existence of many sibling tools, the description is incomplete. It does not explain the effect of revocation, potential dependencies, or return information, especially since no output schema is provided.

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 description mentions 'by code' corresponding to the 'code' parameter, but does not explain what the code is or how to obtain it. With schema coverage at 50%, the description fails to compensate and adds no meaningful parameter semantics.

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 uses the verb 'Revoke' and identifies the resource 'invite by code', which clearly states what the tool does. It distinguishes from sibling tools like discord_create_invite, discord_accept_invite, and discord_get_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 no guidance on when to use this tool vs alternatives, no prerequisites, and no when-not-to-use context. It is a single sentence without usage instructions.

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