dosai_send_operator_messageSend a message to a real client in WhatsApp or Telegram, as a human operator. This is visible to a real person and cannot be unsent, so confirm the wording with the user before calling.
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | Exactly what the client will see. | |
| project_id | Yes | Project id, as returned by dosai_list_projects. | |
| conversation_id | Yes | Conversation id, as returned by dosai_list_conversations. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds crucial behavioral context beyond annotations: the message is visible to a real client, cannot be unsent, and requires confirmation. This is valuable for an irreversible write operation.
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?
Two focused sentences: the first states the action, the second delivers the critical caution. Concise and front-loaded with no filler.
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?
The description adequately covers purpose, target, and the key behavioral risk for a simple send tool with no output schema. Lacks success/error details, but those are less critical given the strong cautionary guidance.
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 descriptions cover 100% of parameters, including 'text' as 'Exactly what the client will see.' The description adds no new parameter-level detail, so it does not exceed the schema baseline.
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?
States a specific action ('Send a message to a real client') with channels (WhatsApp or Telegram) and role (as a human operator), clearly distinguishing it from sibling read/list/update tools.
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?
Provides clear context: the message goes to a real person and cannot be unsent, so confirm wording before calling. This implies when to use (operator response) and cautions against misuse, though it does not explicitly name alternatives (none exist among siblings).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.