discord-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a 'get' operation (implying read-only), but doesn't mention authentication requirements, rate limits, error conditions, or what happens if no screening form exists. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence that communicates the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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?

For a single-parameter read operation with no output schema, the description provides adequate basic information about what the tool retrieves. However, without annotations or parameter documentation, there are significant gaps in understanding authentication requirements, error handling, and the structure of the returned data. The description meets minimum viability but leaves important contextual questions unanswered.

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 doesn't mention the 'guild_id' parameter at all, and with 0% schema description coverage, the parameter is undocumented in both schema and description. However, since there's only one parameter, the baseline is higher. The description implies this tool operates on a guild's membership screening, which gives some context for the required guild_id parameter.

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 ('Get') and resource ('current membership screening form'), explaining what the tool does. It adds helpful context about what the form contains ('rules/questions new members must complete'). However, it doesn't explicitly differentiate from sibling tools like 'discord_update_membership_screening' beyond the 'get' vs 'update' distinction.

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 versus alternatives. There's no mention of prerequisites, when this operation is appropriate, or how it differs from related tools like 'discord_get_guild_info' or 'discord_update_membership_screening'. The agent must infer usage from the tool name alone.

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