discord_move_member_voice

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

With no annotations provided, the description carries full behavioral burden. It reveals the tool mutates voice channel membership, requires the member to be connected, and that omitting channelId disconnects. However, it does not disclose permission requirements, error behavior (e.g., if member not connected), or rate limits, leaving some gaps.

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 two sentences, front-loaded with the action, and every word adds value. It is concise without sacrificing essential information.

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 3 parameters and no output schema, the description covers the primary use case and the special case of disconnection. However, it lacks descriptions for the required parameters (userId, guildId) and does not mention validation or return behavior, which would make it fully complete.

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%, so the description must add meaning. It explains the role of 'channelId' (omit to disconnect) but does not describe 'userId' or 'guildId'. The description partially compensates for the lack of schema documentation but leaves key parameters undefined.

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 moves a member to another voice channel, with the condition 'they must already be connected' and explains the disconnect behavior. Although a sibling 'discord_modify_user_voice_state' exists, the description does not explicitly differentiate, but the purpose is specific and unambiguous.

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 a prerequisite (member must be connected) and a usage hint (omit channelId to disconnect), but does not mention when not to use this tool or suggest alternatives like discord_set_voice_state. Usage guidance is implied but not comprehensive.

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