discord_list_invites

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so 'Read-only' is redundant, but 'Requires the Manage Server permission' is real added context the agent cannot get from structured fields and will prevent failed calls. No disclosure of pagination or behavior when the server has zero invites, which keeps it below a 5.

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 tight sentences, front-loaded with purpose and scope. The parenthetical field list and 'Read-only' partly restate what the output schema and annotations already provide, so a small amount of text does not earn its place.

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?

Output schema exists, so return-value explanation is not required, yet the description still signals what the invite entries contain. With safety covered by annotations, the permission requirement and sibling routing are added, the agent has everything needed to call this correctly.

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?

Only one parameter, documented at 100% coverage in the schema as a snowflake guild ID, so the baseline is high. The description correctly frames the scope as an entire server rather than a channel, which clarifies what guild_id means in this operation even without adding new format detail.

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?

States a specific verb and resource ('List all active invites across a server') plus the fields returned, and explicitly distinguishes itself from the channel-scoped sibling. An agent can pick between discord_list_invites and discord_list_channel_invites without opening either schema.

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?

Names the alternative (discord_list_channel_invites) and the exact condition that selects it (scope to one channel), and states the permission prerequisite for this path. Nothing about when to use one versus the other is left to inference.

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