Bot API Send

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

With empty annotations, the description partially carries the burden by stating 'requires a valid API key' and supporting text/media. However, it does not disclose side effects, delivery guarantees, authentication failure behavior, or rate limits. Add some transparency but not enough for a full understanding.

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 sentences, front-loaded with purpose, no redundancy. Every word adds value.

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?

Despite having 6 parameters, no output schema, and no annotations, the description is minimal. It does not cover error handling, response format, or behavioral nuances (e.g., what happens with mediaUrl when missing messageType). Incomplete for the complexity of the tool.

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 100%, so the schema already describes all parameters. The description adds broad context ('supports text and media messages') but does not add meaning beyond what's in the schema. Baseline 3 is appropriate.

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 an outbound message') and the resource ('bot API', 'specified phone number'). It mentions support for text and media, but does not differentiate from sibling tools like neuron_send_message or neuron_send_broadcast.

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 on when to use this tool versus alternatives (e.g., neuron_send_message). No prerequisites or context provided beyond 'requires a valid API key', which is a requirement but not usage guidance.

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