mirlo_send_message

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

With no annotations, the description carries full burden for behavioral disclosure. It does not mention authentication, rate limits, delivery status, cost, or side effects. 'Send a message' implies a write operation, but no details about response or errors are given.

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 short single sentence (10 words) without redundancy. While concise, it sacrifices completeness; however, every word serves purpose, making it efficient.

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 tool is simple (3 params, no output schema, no annotations), but the description omits critical context such as return value, error handling, consent requirements, or recipient validation. It is insufficient for an agent to use correctly without additional knowledge.

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 coverage is 67%, with channel lacking a description. The tool description adds 'WhatsApp or SMS' which mirrors the channel enum, offering no additional meaning. For to and body, schema format hints are not expanded; thus the description does not compensate for missing param details.

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 tool sends a WhatsApp or SMS message to a phone number, specifying the exact action (Send), resource (message), and target (phone number). It is distinct from sibling tools like mirlo_send_template, which sends templates, and others focused on accounts, contacts, or deals.

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 such as mirlo_send_template, or any prerequisites like requiring a valid contact or consent. The description lacks explicit usage context.

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