WhatsApp Business analytics

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

With no annotations, the description bears full responsibility for behavioral disclosure. It indicates a read-only GET operation but does not mention authentication needs, rate limits, pagination, or whether the request is idempotent. The description provides minimal behavioral context beyond the endpoint.

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?

The description is extremely concise, consisting of a single sentence that packs the endpoint, parameters, and data type. No superfluous words. The structure front-loads the key information, making it easy to parse quickly.

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?

Given the lack of output schema, the description does not explain the return format or what the analytics data looks like (e.g., a list of objects, aggregated counts). It also omits error handling, potential response sizes, and the behavior of optional parameters. The tool has 6 parameters with 4 required, but the description provides insufficient context for effective use.

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%, so the description must add meaning. It explains that start and end are Unix timestamps in seconds, and implies phone_numbers and country_codes are filters ('by phone number, by country'). However, it does not describe waba_id, granularity options (HALF_HOUR, DAY, MONTH), or the effect of these filters. The endpoint format adds some context but leaves significant gaps.

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?

The description clearly states the tool retrieves WhatsApp Business analytics messages sent/delivered/read by phone number, by country, etc., and provides the endpoint format. It specifies the resource ('analytics') and action (GET), distinguishing it from sibling analytics tools that target other platforms (e.g., insights, page_insights). However, it lacks detail on the response structure, which could improve clarity.

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?

No guidelines are provided for when to use this tool versus alternatives like insights or page_insights. The description does not mention prerequisites, such as requiring a WhatsApp Business Account ID, or note constraints like date range limits. There is no guidance on when not to use it.

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