discord_admin_invites

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

The description states deletion is not available in this tool (it's via the raw admin tool), but annotations include destructiveHint: true. This is a contradiction. No other behavioral details are disclosed.

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 two sentences, front-loaded with the main action, and every word adds value. It is concise and well-structured.

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 tool has no output schema and the description does not explain return values or the expected data payload for create operations. The deletion pointer is helpful, but missing details about parameters and behavior make it only minimally complete.

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 50%, with data and reason having descriptions while channelId lacks description and operation only has an enum. The description does not add parameter-specific meaning beyond the schema, but the enum values (list_guild, list_channel, create) are self-explanatory and align with the description.

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 tool lists or creates invites for servers/channels, using specific verbs and resource. It also distinguishes itself from the raw admin tool by noting deletion is available there.

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 explicitly points to the guarded raw admin tool for deletion, providing a clear alternative. It does not elaborate on when to prefer this over other admin tools, but the list/create scope is evident from the description and sibling context.

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