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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds the consequential detail that publishing is not reversible and that a published flow is retired rather than edited. It also discloses the external upload to Meta, which is meaningful behavior beyond the annotation set.

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 tight sentences, front-loaded with the action and outcome, then precondition, then irreversibility. There is no filler or restatement of the name.

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 one-parameter mutation with no output schema, the description supplies everything needed: effect, precondition, the sibling to call first, and the lifecycle alternative. Nothing required to invoke it correctly is missing.

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% and the single parameter is only typed as an integer with minimum 1. The description constrains the target implicitly by insisting it must be a draft with a current, error-free compliance report, which adds real meaning, but it never states what flow_id refers to or how to obtain it.

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 (publish), the resource (WhatsApp Flow draft), and the concrete effect (uploaded to Meta, becomes sendable to customers). This clearly separates it from siblings like deprecate_whatsapp_flow, check_whatsapp_flow, and patch_whatsapp_flow_text.

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?

Explicit preconditions: only a draft can be published, and only when the stored compliance report was run on the current draft and is error-free. It names check_whatsapp_flow as the prerequisite step and deprecate_whatsapp_flow as the alternative to editing.

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