set_nickname

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose one genuinely useful trait the schema cannot convey: passing null clears the nickname rather than setting it. It omits permission requirements, failure modes (e.g. hierarchy/ownership restrictions), and rate-limit behavior for repeated renames.

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?

A single short sentence with zero filler, and the clearing behavior is stated inline where it is most needed.

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?

This is a mutation tool with no annotations, no output schema, and three required parameters undocumented in both schema and description. The description covers only the nickname semantics and leaves an agent without enough information to call it safely or predict failures.

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 0% across four parameters, so the description must compensate and largely does not. It clarifies the semantics of 'nick' (null clears it) but says nothing about 'guild_id', 'user_id', or 'reason' — notably that reason is an audit-log justification rather than part of the change.

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 names a specific verb and resource ('Define ... o apelido de um membro') and no sibling tool overlaps with nickname management, so the agent can identify the operation. It does not, however, explicitly contrast itself with siblings like search_members or edit_role.

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?

There is no guidance on when to use this tool versus alternatives, nor on prerequisites. An agent is not told that changing another member's nickname typically requires elevated permissions, or that a reason may be needed for audit logging.

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