Single tool with partial schema definition and minimal parameter descriptions. Tool name follows verb_noun convention (send_message) but parameter descriptions lack actionable detail. Input schema present but descriptions are generic. No output schema documented. No error handling guidance for LLM recovery. WAHA-specific implementation details (chat_id formatting, session hardcoding) are not abstracted or explained in descriptions.
Envia mensagem via WhatsApp com nome ou telefone.
Parameter descriptions lack actionable constraints and format guidance. 'phone' parameter has no format specification (accepted formats, example), 'name' provides no fallback behavior documentation, 'message' has no length constraints or encoding details.
No output schema documented. Response is a free-form string (success/error message). LLMs cannot reliably parse whether the operation succeeded, which message was sent, or what retry strategy applies. Should return structured JSON with success flag, phone_sent_to, timestamp, and error details if applicable.
Error responses lack recovery guidance. Generic errors like 'Erro de conexão: <str(e)>' and 'Erro do WAHA: {response.text}' do not tell the LLM whether to retry, wait, or escalate. No error classification (retryable vs. user-fixable vs. fatal).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 44 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 6 | - | v1 |
Parameter interdependency undocumented. Tool accepts 'phone' and 'name' but only one is required. CONTACTS dictionary is hardcoded and not documented in the parameter description. LLM has no way to know which contacts are available or how to construct phone numbers.
No idempotency guarantee documented. Tool calls external WAHA API with timeout=30s but provides no idempotency key or duplicate detection. If LLM retries on timeout, message may be sent twice. Description does not warn of this risk.
Tool combines two separate concerns: contact lookup and message transmission. Tool name 'send_message' suggests a single action but implementation branches on 'phone' vs 'name' parameter. Should split into 'resolve_contact' + 'send_message_to_phone' or provide explicit 'lookup_contact' as a resource or separate tool.
Hardcoded session name and WAHA endpoint. SESSION_NAME='default' and WAHA_URL='http://localhost:3000/api/sendText' are not configurable via tool parameters or environment variables. Tool is tightly coupled to a specific local deployment, reducing reusability and making configuration opaque.