set_default_whatsapp_account

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

No annotations exist, so the description carries the full behavioral burden. It discloses the key side effect (changing the default account for whatsapp_* tools), but says nothing about prerequisites like whatsapp_connect, whether the chosen account must already exist, whether the change persists, or how to select the account given the empty schema.

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, front-loaded sentence with no filler. It immediately names the action and the effect, which is appropriate for a zero-parameter configuration tool.

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 configuration tool with no output schema and no annotations, the description states the effect adequately. However, it leaves a notable gap: it says 'choose which account' while the schema exposes no way to choose one, so an agent lacks the mechanism and any prerequisite context.

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?

The tool has zero parameters and the schema is empty, so the baseline is 4. The description correctly references the `account` argument of other whatsapp_* tools rather than introducing parameters this tool does not have.

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 (choose/set as default) plus the resource (WhatsApp account) and the scope of the effect (default for whatsapp_* tools when no account is given). An agent can distinguish it from whatsapp_list_accounts and the other whatsapp_* action tools without opening a 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?

The description implies the usage context ('when no `account` is given') but never explicitly says when to use this tool versus alternatives such as specifying the account per call or using set_default_telegram_account. It provides implied usage only, not explicit guidance or exclusions.

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