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

With readOnlyHint and openWorldHint already declared, the bar is lower, but the description still earns credit by enumerating the returned fields (flow id, name, status, categories, entry screen) — valuable since there is no output schema. It doesn't cover pagination or result-size behavior, keeping it from 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 tight sentences: scope and return shape first, then the intended use. Zero filler and every clause carries 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 read-only filtered-list tool with no output schema, the description covers what it returns and what it's for, which is enough to invoke it correctly. Missing only secondary details like result limits or ordering.

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 100%, so both the device ID format and the status enum are fully documented in the schema. The description only restates 'for a device (WABA)' and adds no format or filtering semantics beyond that, so the baseline of 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 and resource ('List WhatsApp Flows') and clarifies the scope as per-device (WABA), which distinguishes it from sibling tools like list_whatsapp_flow_responses and list_whatsapp_templates. It doesn't explicitly name which sibling to use instead, but the resource noun is unambiguous.

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?

'Use this to find a flow to send' implies the downstream action (send_whatsapp_flow) but never names it or states explicit when-not conditions. Usage is inferable rather than stated, so it lands at minimum viable guidance.

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