mute_member

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

Annotations already indicate mutation (readOnlyHint=false) and idempotency (idempotentHint=true). Description adds 'Mutates the group by muting a member' and default duration, but lacks details on error states or behavior when bot lacks privileges.

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 short, front-loaded with the purpose, and efficient. However, it repeats parameter explanations that could be inferred from the schema, making it slightly less concise.

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?

Covers the main points: purpose, parameters, prerequisite, and reversal. Lacks details on error handling or behavior when member is already muted. Acceptable for a simple mutation tool with no output schema.

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?

Despite 0% schema description coverage, the description explains each parameter: group_id as QQ group number, user_id as QQ number, and duration with default 600 seconds. This adds meaning beyond the schema's type/title only.

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 'Mute a member in a QQ group' and explains parameters. It mentions unmute_member as a sibling tool but does not explicitly differentiate from other sibling tools like kick_member or set_member_card.

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?

Description includes prerequisite 'Requires bot to have admin privileges' and suggests unmute_member for reversal. However, it does not provide guidance on when to prefer mute over other mutation tools like kick_member.

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