unmute_member

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

Describes mutation effect ('Mutates the group by unmuting a member'), idempotency (no-op if already unmuted), and admin privilege requirement. Adds value beyond annotations which already indicate idempotent and non-destructive.

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?

Multiple sentences but each adds essential information (action, parameters, requirements, behavior, alternatives). Front-loaded with main purpose. Could be slightly shorter but still efficient.

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 no output schema, description covers return behavior (success), idempotency, and prerequisites. Sufficient for a simple mutation tool. Annotations already cover safety and idempotency.

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?

Adds context to both parameters by calling group_id a 'QQ group number' and user_id a 'QQ number', clarifying their meaning beyond the schema's generic titles. Schema coverage 0%, so description compensates well.

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?

Clearly states 'Unmute a member in a QQ group', providing specific verb and resource. Distinguishes from sibling 'mute_member' by mentioning it. No ambiguity.

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?

Provides explicit when-to-use (when member is muted), when-not (no-op if not muted), prerequisites (admin privileges, check member list via get_group_member_list), and alternatives (mute_member). Comprehensive guidance.

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