Discord Server Setup MCP

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

No annotations are provided, so the description carries the full burden. It discloses that this tool sets a stateful context affecting subsequent operations, which is valuable behavioral information. However, it doesn't mention potential side effects like permission requirements, error conditions, or whether the selection persists across sessions.

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 perfectly concise with two sentences that are front-loaded and essential. Every word contributes to understanding the tool's purpose and usage without any redundancy or unnecessary elaboration.

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 tool's moderate complexity (stateful context setting) and lack of annotations/output schema, the description is mostly complete. It explains the core behavior and scope, though it could benefit from mentioning any limitations or prerequisites. The absence of an output schema is acceptable here as the tool likely doesn't return complex data.

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 100%, so the schema already documents the single parameter 'guildId' with its type and description. The description doesn't add any additional parameter semantics beyond what the schema provides, maintaining the baseline score.

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 specific action ('Sets the active Discord server') and resource ('guild'), distinguishing it from siblings like get_guild_info (which retrieves information) or list_guilds (which lists available servers). It precisely defines what the tool does beyond just its name.

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 states when to use this tool ('for subsequent operations') and provides clear context about its effect ('All tools will use this server unless a different guildId is explicitly specified'), helping differentiate it from alternatives that might directly specify guildId in each call.

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