Create a community

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

With no annotations, the description carries the behavioral disclosure burden. It reveals a key non-obvious constraint: members are not added directly to a community; they join via its groups. However, it does not mention permissions, what happens to groups passed in link_groups, or what the operation returns, leaving meaningful gaps.

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 three sentences with no filler: it defines the resource, clarifies the membership model, and directs the next action. Every sentence contributes value and the key information is front-loaded.

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 relatively simple creation tool with no annotations and no output schema, the description gives solid conceptual grounding and workflow guidance. It does not mention operational prerequisites or the full effects of link_groups, but for an agent familiar with common API patterns this is mostly complete.

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%, so the schema already documents all three parameters. The description adds useful context about communities and groups but does not meaningfully elaborate on parameter semantics beyond what the schema provides, so the baseline score 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 states a specific action and resource: creating a WhatsApp community. It defines what a community is (an umbrella that holds groups with an announcement channel) and distinguishes itself from sibling tools by explicitly pointing to link_group_to_community and create_group for adding groups.

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 explains that members join through groups, not directly, and gives explicit next-step guidance: use link_group_to_community or create_group(community=...) after creating. It could be more explicit about when not to create a community, but the conceptual framing makes the intended workflow clear.

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