discord_get_guild_vanity_url

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description usefully adds the feature-gating prerequisite that annotations cannot express. It stops short of saying what happens if the feature is missing (error vs. null return), which would have made it fully transparent.

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 short sentences, each doing distinct work: purpose, prerequisite, safety, and the pre-check routing. Front-loaded with the definition and no filler.

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?

An output schema exists so return values need no explanation, the only parameter is fully documented in schema, and the description covers the one non-obvious hazard (feature gating) plus a verification path. Nothing an agent needs to call it correctly is missing.

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?

Single guild_id parameter with 100% schema description coverage including a snowflake pattern, so the schema carries the parameter semantics. The description adds nothing about the ID itself, which is acceptable at this coverage level.

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 ('Read the server's vanity invite URL') and defines the term inline ('the custom discord.gg link'), which distinguishes it from the many invite-related siblings like discord_get_invite and discord_list_invites.

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?

Explicitly names the prerequisite ('Requires the VANITY_URL feature') and routes the agent to a specific sibling ('Use discord_get_guild_features to check whether the feature is active first'), giving both the condition and the alternative.

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