discord_set_nickname

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

Annotations already indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true). The description adds valuable behavioral context: how to clear the nickname (using null or the string 'null'), permission requirements, and audit log recording—all beyond what annotations provide.

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?

The description is three sentences: purpose, null handling, and permissions/audit log. Every sentence adds essential information without redundancy. Front-loaded with the main action.

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?

Given the annotations (idempotentHint=true, readOnlyHint=false) and complete schema descriptions, the description provides sufficient behavioral context (permissions, null handling, audit log). No output schema is present, but return value is likely a simple status, which is common for mutations.

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 descriptions cover 100% of parameters. The description adds value by explaining that null (or the string 'null') clears the nickname, which is useful but already implied by the schema. This nuance helps the agent handle edge cases correctly.

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 clearly states the tool sets or clears a member's server nickname (verb+resource). It distinguishes from sibling tools like discord_ban_member or discord_send_message by focusing solely on nickname modification.

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?

The description specifies required permissions (Manage Nicknames or Change Nickname) and notes that the reason is recorded in the audit log. It does not explicitly state when to use vs. alternatives, but the context is sufficient for correct usage.

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