discord_get_invites

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

The description discloses only that it lists invites (a read operation), but with no annotations provided, it fails to mention permissions, rate limits, or the nature of the response. The behavioral transparency is minimal.

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—one sentence with no unnecessary words. It is front-loaded, but could be slightly more informative 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 presence of sibling tools like discord_get_channel_invites and discord_get_invite, the description should clarify scope (guild-wide vs channel-specific) and mention what data is returned. It does not provide enough context for proper use.

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 schema has 0% description coverage for the single parameter guildId, and the tool description adds no additional meaning or constraints. The parameter 'guildId' is left completely unexplained, forcing the agent to infer its type and role from the name alone.

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 verb 'List' and the resource 'a guild's invites', indicating the tool retrieves all invites for a guild. However, it does not distinguish from similar sibling tools like discord_get_channel_invites or discord_get_invite, which could cause confusion.

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?

No guidance is provided on when to use this tool versus alternatives such as discord_get_channel_invites (for channel-specific invites) or discord_get_invite (for a specific invite). The description lacks context for appropriate selection.

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