create_server

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

No annotations are provided, so the description carries the full burden, and it does disclose one important behavioral constraint (the 10-guild bot limit) that an agent could not infer from the schema. However, it omits required bot permissions, what happens on failure (error shape), whether the bot auto-joins the created guild, and what the response contains.

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?

Two tight sentences with zero filler: the purpose leads and the critical operational caveat follows. Nothing is redundant with the name or schema.

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?

With no annotations and no output schema, the description still covers purpose plus the single biggest gotcha for this operation, which is strong for a 2-parameter creation tool. It is slightly short of complete because it never says what a successful call returns (the created guild object) or what permissions/errors to expect.

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% for both parameters (name, iconUrl), including the base64/data-URI detail for the icon, so the schema already does the heavy lifting. The description adds nothing about parameter format or constraints, so the baseline 3 applies.

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 opens with a specific verb+resource ('Create a new Discord guild'), which is unambiguous and easily separated from the many other create_* siblings that target channels, roles, emojis, threads, or invites. The clarifying note reinforces that guild == server, matching siblings like get_server_info and list_servers.

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?

It gives a concrete precondition that governs when the call will succeed: bot accounts can only create guilds while in fewer than 10 guilds. That effectively states a when-not condition, but it does not mention permission requirements or any alternative approach (there is no sibling that creates a guild, so alternatives are moot).

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