update_member

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

The annotations already indicate a destructive write operation (readOnlyHint false, destructiveHint true). The description adds some specificity by naming the modifiable fields, but does not disclose potential side effects such as removing roles or resetting timeouts.

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 a single, clear sentence that front-loads the verb and target. It is concise and free of unnecessary words.

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?

The tool involves a nested 'data' object, yet the description does not explain its structure or permissible values. Without output schema or parameter details, the description is insufficient for correct usage, especially given the destructive nature.

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?

The description provides no details about the parameters. The schema has three required fields (guild_id, user_id, data) with zero description coverage. The phrase 'using Discord fields' does not explain what 'data' should contain, so the agent cannot construct a valid request.

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 ('Modify') and the resource ('member'), and explicitly lists the affected fields (nickname, roles, timeout, mute, voice channel). This distinguishes it from sibling tools like add_member_role or remove_member_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?

No guidance is provided on when to use this tool versus alternatives like add_member_role or remove_member_role. It does not mention whether this is for combined updates or specific scenarios.

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