whatsapp_set_community_picture

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

Adds two behavioral facts beyond the annotations: the call needs admin rights and the change applies to all members by replacing the existing picture. Given idempotentHint=true and destructiveHint=false are already supplied, this is solid added context, though it doesn't quantify propagation delays or failure modes.

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 sentences, each earning its place: what it does, the admin prerequisite and blast radius, and the return behavior. Purpose is front-loaded with zero 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 two-parameter mutation with no output schema, the description covers purpose, permission requirement, scope of effect, and return shape ('success confirmation'). Only minor gaps remain, such as image size limits or how a failed permission check surfaces.

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 'id' (Community JID) and 'data' (base64 JPEG) are fully documented in the schema. The description's mention of 'base64 image data' adds no format detail beyond that, so the baseline of 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 ('Set a community's profile picture') plus the input medium ('from base64 image data'), clearly distinguishing it from the sibling whatsapp_set_group_picture and the various get/set community settings tools.

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?

Gives a clear prerequisite ('Requires admin rights'), which tells the agent when the call is viable. It stops short of naming an alternative or stating when not to use it, so it is clear context rather than full when/when-not routing.

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