whatsapp_set_community_name

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

Annotations already declare the safety profile (idempotent, non-destructive, open-world), so the bar is lower, and the description still adds real context: the admin-rights requirement and the fact that all members see the change. It also states the return shape. It stops short of noting any rate limits or propagation delay, so a 4 rather than a 5.

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?

Three short clauses, front-loaded with the action, then the precondition, then the side effect and return. No filler and nothing redundant.

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 two-parameter mutation with no output schema, the description covers the operation, its permission gate, its visibility impact, and what it returns. That is nearly everything an agent needs; only edge cases like name validation rules are unaddressed.

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% with both parameters documented (Community JID, New name), so the schema already carries the semantics. The description adds no syntax, length, or uniqueness constraints beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Rename a community'), which cleanly separates it from the other community mutators in the sibling list such as set_community_description, set_community_picture, and set_community_locked. An agent can select it without opening the schema.

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 gives one useful precondition ('Requires admin rights'), which tells the agent when the call will fail, but it names no alternatives and gives no guidance on when renaming is appropriate versus other community updates. Usage is implied by the narrow verb, so this is minimally viable rather than explicit.

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