whatsapp_update_my_profile

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

Annotations already declare non-readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond them: contacts see the change (external visibility), partial-update behavior, and that a success confirmation is returned.

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?

Four short sentences, each doing distinct work (purpose, visibility effect, partial-update rule, return value), with the purpose front-loaded and no filler.

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 mutation with annotations and no output schema, the description covers what changes, who sees it, partial-update semantics, and the response. It omits error/failure behavior and any size or format constraint on the picture, which are minor residual gaps.

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 coverage is 100%, so the baseline is 3, but the description adds the crucial semantic that only supplied fields are updated — important because all three parameters are optional. It also names the three fields in user terms, though it calls the 'status' parameter 'about text', a minor terminology drift from the schema.

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 (change) and precise resource scope (the connected number's own display name, about text or picture), which cleanly separates it from siblings like whatsapp_get_my_profile and whatsapp_update_group_name. An agent can identify the operation 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?

Usage is implied rather than stated: it describes partial-update semantics (only passed fields change) and contact visibility, but never names an alternative tool or says when to call this versus whatsapp_get_my_profile. Adequate context, no explicit routing.

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