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

Annotations already indicate a non-read-only, non-destructive operation. The description adds the endpoint and 'static or dynamic template' detail but does not disclose side effects like async behavior, rate limits, or report generation. With annotations covering the safety profile, a moderate score is appropriate.

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 concise sentence, front-loaded with the key action and resource, and includes the endpoint. No unnecessary words or repetition of schema details.

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 moderate complexity, presence of an output schema, and robust annotations, the description is largely complete. It covers the core purpose and differentiates through the endpoint, though it could explicitly state that this is for bulk broadcasts versus one-on-one messaging. Overall sufficient enough for an agent to select 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?

Schema description coverage is 100%, so the schema already fully documents all parameters. The description adds minimal semantic value beyond the schema, mentioning static/dynamic templates but not directly explaining how parameters map to that behavior. Baseline 3 is warranted.

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 that the tool sends a WhatsApp template broadcast via a specific endpoint. It uses a specific verb ('Send') and resource ('WhatsApp template broadcast'), and it distinguishes from sibling tools like create-whatsapp-template or get-whatsapp-broadcast-report by focusing on the send action.

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 implies usage for sending broadcasts but provides no explicit guidance on when to use this tool versus alternatives like send-user-message or send-inbox-message. It does not mention exclusions or alternatives, leaving the decision to the agent's inference.

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