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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds that results carry id and status and that only PUBLISHED flows are sendable, which is genuine extra context, but it says nothing about pagination, result ordering, or volume of flows returned for a read-list tool.

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 padding, scope stated first and the published-only constraint placed last as a decisive caveat. Every clause earns its place.

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 simple read-only single-parameter list tool with no output schema, the description covers what is returned and the key constraint. It is nearly complete; the only omission is pagination/volume behavior, which is minor given the tool's simplicity.

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?

There is a single parameter (accountId) with 100% schema description coverage, including the pointer to list_accounts, so the schema does the heavy lifting. The description adds nothing about the parameter, which is the expected baseline 3 at this coverage level.

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 (lists WhatsApp Flows for an account) and adds a clarifying gloss that flows are in-WhatsApp forms for booking/qualifying/ordering, which separates them from the similarly-named templates sibling. It also states the returned fields (id and status). It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

'Only a PUBLISHED flow can be sent' implies the downstream purpose (finding a flow to send via send_whatsapp_flow), so usage is inferable. However, there is no explicit when-to-use statement, no mention of when to prefer this over get_whatsapp_flow_responses or list_whatsapp_templates, and no prerequisites.

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