waba_list_conversations

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

With no annotations, the description carries the burden and it provides meaningful behavioral context: the list is filtered to the 24-hour customer service window, and these are the only recipients eligible for free-text replies. It does not describe output format or pagination behavior, but the primary behavioral rule is clearly disclosed.

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 concise sentences with no filler. The core condition (24-hour customer service window) is front-loaded, and the practical consequence (free-text reply eligibility) follows immediately.

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 paginated list endpoint with no output schema, the description captures the essential selection logic an agent needs to decide to call it. It could mention the response shape, but the schema already covers paging and the tool's purpose is well-defined.

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%: page and limit already have descriptions in the input schema. The tool description adds no extra meaning or constraints beyond the schema, so the baseline score 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?

Description uses a specific verb ('List') and a precise resource: customers/conversations still inside the 24-hour customer service window. This clearly distinguishes it from messaging siblings like send_message, send_waba_template, and waba_reply, which perform sending actions rather than listing.

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?

The description communicates when the tool matters: before replying with free text, you need the list of numbers eligible instead of templates. It does not explicitly name alternative tools or state when not to use it, but the context is clear enough for an agent to select this tool appropriately.

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