discord_set_nickname

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

Annotations indicate it's idempotent and not read-only or destructive. The description adds context about the audit log recording the reason, which goes beyond annotations. No contradictions.

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 concise sentences, each fulfilling a role: core action, usage nuance, and permission/audit note. No wasted words, and the information 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 mutation tool with excellent annotations and schema, the description covers all necessary aspects: action, parameters, permissions, and side effects. No missing context.

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%, but the description adds valuable clarifications: how to clear the nickname (null or 'null' string), max 32 characters for the nickname, and the optional reason for audit logs. This enhances schema meaning.

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 action: 'Set or clear a member's server nickname.' The verb is specific ('set' or 'clear'), and the resource is a 'server nickname', distinguishing it from sibling tools that deal with other Discord entities like roles or bans.

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 provides explicit permission requirements and explains how to clear the nickname (pass null). It doesn't explicitly mention when not to use this tool, but given the unique purpose, the guidance is sufficient.

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