discord_modify_user_voice_state

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

With no annotations provided, the description carries the burden of disclosing behavior. It explains the effect of the 'suppress' parameter (false=invite to speak, true=move to audience), which is helpful. However, it does not mention required permissions (e.g., 'Requires moderator privileges'), side effects, or the return value.

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 sentence that is concise and front-loaded. It contains no filler or redundant information, and every word adds valuable context. It is optimally sized for quick comprehension.

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 4 parameters, no output schema, and no annotations, the description is incomplete. It does not explain three required parameters (userId, guildId, channelId) or any constraints (e.g., channelId must be a stage channel). The tool's return value is also omitted. While the description covers core behavior, it lacks critical details for reliable invocation.

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 0%, so the description must explain all parameters. It only explains the 'suppress' parameter, leaving 'userId', 'guildId', and 'channelId' undefined. The description implicitly suggests 'channelId' is a stage channel, but fails to clarify the role of each parameter. This is insufficient for correct invocation.

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's purpose: 'Stage moderation: invite a user to speak (suppress:false) or move them to audience (suppress:true).' It uses specific verbs (invite/move) and identifies the resource (user voice state in stage). This distinguishes it from sibling tools like discord_set_voice_state (self-modify) and discord_move_member_voice (voice channel move).

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 implies usage for stage channel moderation ('Stage moderation:') but does not explicitly state when to use or avoid this tool compared to alternatives. It lacks explicit exclusions or prerequisites (e.g., 'Only works in stage channels'). However, the context is clear enough for an AI to infer appropriate use.

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