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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds the HTTP method POST, which is useful context for a read operation and does not contradict annotation hints. No additional behavioral details (e.g., date handling) are provided, but the annotations carry the safety profile.

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 a single, compact sentence that immediately states the tool's core action and endpoint. No filler or redundancy; it is front-loaded and efficient.

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 tool's simplicity, the annotations, and the presence of an output schema, the description sufficiently covers the essential behavior. Minor gaps exist (e.g., date format expectations) but these are not critical for an agent to select and invoke the tool correctly.

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?

The input schema provides 100% coverage with descriptions for all three parameters (start_date, end_date, and status with enum values). The description itself adds no parameter-specific meaning, so baseline 3 is appropriate when the schema already documents parameters.

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 action (Fetch), the resource (WhatsApp broadcast delivery stats), and the specific endpoint (POST /v1/whatsapp-broadcast-report). This distinguishes it from sibling tools like send-whatsapp-broadcast and get-bot-dashboard-stats.

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 clearly conveys the tool's purpose as a retrieval/report tool for WhatsApp broadcast delivery stats, which implies usage when delivery information is needed. It does not explicitly name alternative tools or exclusion scenarios, but the context is unambiguous given the sibling set.

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