send_whatsapp_message

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

With no annotations provided, the description must fully convey behavioral traits. It reveals the critical 24-hour window constraint but does not disclose other behaviors such as whether the tool is mutative, error handling, or permission requirements. This is adequate but not comprehensive.

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 two sentences long, with the primary action stated first and the critical constraint following. No unnecessary words or redundancy.

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 absence of annotations and output schema, the description covers the key use-case constraint. It does not specify return values or prerequisites, but for a simple send operation this is acceptable and fairly complete.

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 has 100% coverage, so the baseline is 3. The description does not add new meaning beyond the schema; it mentions 'existing conversation' which aligns with cardId but does not clarify the auto-resolved parameters (boardId, columnId). Overall, the schema carries the semantic load.

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 explicitly identifies the action as sending a free-text WhatsApp message into an existing conversation, using a specific verb-resource pair. It also clearly distinguishes from the sibling tool send_whatsapp_template by mentioning the 24-hour customer service window.

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 provides explicit guidance on when to use this tool (inside the 24-hour window) and when to use the alternative send_whatsapp_template (outside the window), leaving no ambiguity for the agent.

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