androidapi_send_sms_bulk

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

Annotations already indicate write and non-destructive, so the description adds spintax/shortcode support. However, it does not explain mode (devices vs credits), parameter dependencies, or campaign lifecycle effects. Lacks depth for a tool with 10 parameters.

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 concise sentences, front-loaded with primary action. No redundant info. Every word earns its place.

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?

With 10 parameters, no output schema, and moderate annotations, the description lacks critical context like mode semantics, parameter interdependencies (groups vs numbers), and response format. Incomplete for a bulk SMS campaign 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 only 40% with descriptions for groups, numbers, message, and campaign. Description adds value for 'message' (spintax/shortcodes) but provides no extra meaning for sim, mode, device, gateway, priority, or shortener. Partial compensation for coverage gap.

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 'Send an SMS campaign to multiple phone numbers and/or contact groups' with specific verb (send) and resource (SMS campaign), distinguishing from singular send tools and campaign start tools. Support for spintax and shortcodes adds specificity.

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 explicit guidance on when to use this tool vs alternatives like androidapi_send_sms or androidapi_start_sms_campaign. With many sibling tools, the absence of usage context is a significant gap.

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