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

Annotations already indicate this is a mutating operation (readOnlyHint=false, destructiveHint=false). The description adds a useful behavioral detail beyond annotations: the admin permission requirement under group restrictions. It does not enumerate failure modes or side effects, but the added permission context is genuinely informative.

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 short sentences with no filler. The first sentence front-loads the exact action and resource, and the second sentence adds a relevant condition. Every word earns its place.

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 three-parameter mutation tool with full schema coverage, clear annotations, and an output schema, the description is complete. It covers what the tool does and the key prerequisite, and the input schema covers all parameter details.

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 100%, and the schema already explains each parameter: the max 25-character name, the @g.us JID provenance from wa_list_groups, and the account provenance from wa_list_accounts. The description itself adds no additional parameter-level meaning, so the baseline of 3 is appropriate.

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 opens with 'Rename a WhatsApp group', giving a specific verb and resource. This clearly distinguishes it from sibling tools like wa_set_group_description, wa_set_group_announce, and wa_set_group_locked. The admin caveat adds relevant context without obscuring the core purpose.

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?

It is clear this tool is for renaming a group, and the description provides a meaningful precondition: the account must be an admin if the group restricts settings changes. It does not explicitly name alternatives or state when not to use it, but the context is unambiguous enough for an agent to select it correctly.

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