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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing further — no note that this creates persistent state on the WhatsApp instance, that repeated calls may create duplicate groups (non-idempotent), or what the call returns.

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?

A single short sentence with no wasted words and the action front-loaded. However, brevity here is under-specification rather than disciplined concision — there is room for a sentence or two of genuine value.

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 non-idempotent, open-world mutation requiring three inputs, the description omits whether the instance must be connected, what happens to the participant list, and what the response contains (group ID). There is no output schema, so the description should have said something about the result.

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 all three required parameters (instance_id, group_name, chat_ids with example format) are fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 is effectively a restatement of the tool name 'whatsapp_create_group' — verb 'Create' plus resource 'WhatsApp group'. It does not add specificity such as what is required to create one, what identifiers come back, or how it differs from siblings like whatsapp_add_group_participant.

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?

No when-to-use context, no prerequisites (e.g., instance must be connected), and no mention of the related sibling tools such as whatsapp_add_group_participant or whatsapp_leave_group. The agent must infer everything from the name alone.

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