discord_remove_guild_banner

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

Annotations already declare destructiveHint=true and idempotentHint=true, so irreversibility is partly covered; the description still adds the concrete permission and boost-level gate, which is not derivable from structured fields. It also notes the return value, though an output schema exists. Missing detail on failure modes (what happens if the guild has no banner or lacks boost).

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 carrying distinct information: action, prerequisites, irreversibility plus return. Nothing is redundant and the action is front-loaded.

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 simple two-parameter mutation with rich annotations and an output schema, the description supplies the permission gate, feature requirement, reversibility, and return value — everything an agent needs to decide and invoke correctly.

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 both parameters (guild_id and the optional audit-log reason) are already documented. The description adds no parameter-level meaning and never mentions the reason field, 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?

States a specific verb plus resource: 'Remove the server's banner.' This is unambiguously distinct from the sibling discord_set_guild_banner and discord_remove_guild_icon, which target a different resource.

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 the preconditions for legitimate use ('Requires Manage Server and the BANNER feature (boost level 2+)'), which tells the agent when the call can succeed. It does not name alternatives (e.g., set_guild_banner to replace rather than remove) or describe when not to call it.

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