waha_send_contact

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but fails to mention critical traits like whether this is a mutative operation (likely yes, as it sends data), potential side effects (e.g., notifications to recipients), or error conditions (e.g., invalid contact IDs). This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, 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 complexity of sending data in a messaging app (a mutative operation with potential side effects), no annotations, and no output schema, the description is incomplete. It lacks details on behavior, error handling, or response format, making it inadequate for safe and effective use by an AI agent.

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 documents all three parameters (chatId, contactsId, session) with basic descriptions. The description adds no additional meaning beyond implying that 'contactsId' refers to vCard contacts, but this is minimal enhancement over the schema's documentation.

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 ('Send contact card(s)') and target ('to a WhatsApp chat'), with the specific format 'vCard' providing additional precision. However, it doesn't differentiate from sibling tools like 'waha_send_text' or 'waha_send_file' beyond the content type, missing explicit distinction.

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 guidance is provided on when to use this tool versus alternatives (e.g., 'waha_send_text' for plain text or 'waha_send_file' for files). The description lacks context about prerequisites, such as needing valid chat IDs or session setup, offering no usage instructions.

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