discord_set_bot_nickname

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

Goes well past the annotations (readOnly=false, idempotent=true, destructive=false) by disclosing the exact permission requirements (Change Nickname, or Manage Nicknames if restricted on its own behalf), the null-clearing fallback behavior, and the returned previous/new nickname pair. These are the operational facts an agent needs before a mutation call.

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 sentences, each carrying distinct information, with scope stated first and the operational details after. Slightly denser than necessary — the permission clause is long — but nothing 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?

Covers scope, permissions, null semantics, and return values for a three-parameter mutation tool; an output schema exists, so return shape needs no further detail. Nothing an agent needs in order 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real semantics: null is a meaningful sentinel that reverts to the global username rather than an invalid input. The optional 'reason' audit-log parameter is left to the schema.

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 with an explicit scope qualifier: 'Change the bot's own nickname in one server.' The 'bot's own' and 'per-server' framing separates it cleanly from discord_set_nickname (other members) and discord_set_bot_username (global), without opening either schema.

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?

Makes the selection condition clear through scope: per-server only, does not touch the global username, and null clears the nickname. It does not explicitly name the sibling to use for global changes (discord_set_bot_username) or for other members (discord_set_nickname), so routing is inferable but not spelled out.

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