discord_set_guild_splash

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

Annotations declare mutation, idempotency, and lack of destructiveness, but the description adds the auth/feature-gate requirements (Manage Server, boost level 1+ INVITE_SPLASH) that annotations cannot convey. It also states the removal path and that it returns the new splash URL, which is meaningful behavioral context beyond structured fields.

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?

Four short clauses, front-loaded with the verb and resource, then prerequisites, then the null-removal behavior, then the return value. No sentence is 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-value explanation isn't strictly required, yet the description still notes the returned splash URL. Permissions, feature gate, removal semantics, and behavior are all covered for this low-param mutation tool.

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 image format details live in the schema. The description's 'Pass null to remove it' adds emphasis but largely restates what the schema's anyOf[null] and description already document. Baseline 3 applies given full schema coverage.

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 pair and resource ('Set or remove the server's invite splash') and explains what it is ('background shown on the invite page'). An agent can immediately tell it apart from sibling tools like discord_set_guild_banner or discord_set_guild_icon.

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?

Gives explicit prerequisites ('Requires the INVITE_SPLASH feature (boost level 1+) and Manage Server') and the removal condition ('Pass null to remove it'). It doesn't name an alternative tool, but no sibling performs this same operation, so the guidance is clear in context.

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