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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description goes beyond them by disclosing the workflow consequence that editing components routes the template back through Meta review (status returns to PENDING) – a non-obvious side effect. It stops short of noting that components is a full replacement list or what the response 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?

Three short sentences, front-loaded with the mutation scope, then the review side effect, then the input constraint. No filler; each sentence carries actionable information.

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 destructive mutation with annotations covering safety and no output schema, the description is nearly complete: it names the mutable fields, the constraint, and the review side effect. Minor gap is the absence of any note on permissions or that components must be a full replacement list, though the schema covers the latter.

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 the schema already documents all five parameters, including that components is 'Full replacement component list' and TTL is 'within the category range'. The description repeats the field names and adds the at-least-one requirement but no syntax or format detail beyond the schema, so baseline 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 (update) and resource (WhatsApp template) plus the exact fields being mutated (components, message_send_ttl_seconds). Easily distinguished from siblings like whatsapp_template_create, whatsapp_template_delete, and whatsapp_template_get 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?

Provides one concrete usage rule ('At least one of components / message_send_ttl_seconds is required'), which is genuinely helpful. However, it names no alternative tool and gives no explicit when-to-use/when-not guidance relative to create/delete/get siblings, so usage is only implied.

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