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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered externally. The description adds genuinely new behavioral context: only drafts are deletable and deprecation is the non-destructive path that preserves history and answers. It stops short of stating irreversibility or what happens to an in-flight/published flow rejected by this call, so it falls just short of a 5.

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, zero filler. The operation is front-loaded and the routing constraint follows immediately, with the alternative tool named in the same breath.

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?

No output schema exists, but a delete operation needs little return documentation, and the annotations already carry the destruction/idempotency semantics. The description covers the one real ambiguity (draft vs. published). It could mention failure behavior when a published flow_id is passed, which keeps it from a 5.

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 0% and the single parameter (flow_id) is never mentioned in the description. The name is largely self-explanatory, but the description does nothing to compensate for the missing schema documentation or to say where a valid flow_id comes from (e.g., list_whatsapp_flows).

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 ("Delete a WhatsApp Flow draft") plus an explicit scope restriction (drafts only), which cleanly separates it from the sibling delete_* tools and from deprecate_whatsapp_flow. An agent can distinguish this tool from every sibling 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?

Explicitly names the condition selecting this tool (drafts) and the alternative for the other case ("a published flow is retired with deprecate_whatsapp_flow instead"), including why the alternative exists ("keeps its history and answers"). This is textbook when/when-not guidance.

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