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

Adds real value beyond the annotations by spelling out the reconciliation outcomes — inserts, updates with Meta's approval state, and deletion of records Meta no longer returns — which explains the destructiveHint=true in concrete terms. It does not cover idempotency/cost of repeated runs (annotation says idempotentHint=false) or any rate limits or auth requirements.

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?

Two sentences, front-loaded with the operation and its mirroring semantics, then the operational timing rule. No filler; the parenthetical conveys three distinct behaviors compactly.

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 tool with no output schema, it covers the what, the side effects, and the when-to-call. The remaining gap is the all-optional parameter situation — an agent cannot tell whether a call without any account identifier is valid or what it would sync.

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 0%, so the description carries the burden; it names both parameters and tells us they identify the WhatsApp account and are alternative forms (id vs uuid). It does not resolve precedence if both are supplied, nor what happens when both are omitted given required=0, leaving the agent to guess.

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 ('pull ... templates from Meta and mirror them into the panel') plus the exact reconciliation semantics. It is clearly distinguishable from list_wp_templates, create_wp_template, and send_wp_template in the sibling set.

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 concrete timing guidance: 'Run it before listing templates and after creating one', with the reason (approval arrives from Meta, not the panel). It stops short of naming the sibling tools explicitly or saying when not to run it (e.g. cost/rate concerns on repeated calls).

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