Send bulk SMS

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

Annotations already indicate non-readonly (readOnlyHint=false) and open world (openWorldHint=true). The description adds value by explicitly warning 'High-impact: confirm the list before calling,' highlighting potential consequences beyond the annotations. No contradiction detected.

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 extremely concise with two sentences: the first clearly states the purpose and constraint, and the second adds a critical warning. No unnecessary words, front-loaded and 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?

Given the simplicity of the tool (3 params, no output schema), the description covers the essential context: the operation, the maximum recipients, and a safety note. It could mention response handling or asynchronous nature, but it is largely complete for the use case.

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 description coverage is 100% with each parameter having a description. The tool description does not add any additional parameter meaning beyond the schema, so the baseline score of 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 verb (send), resource (the same SMS to many recipients), and a key constraint (max 500). It effectively distinguishes this tool from siblings like 'send_sms' (single recipient) and 'send_bulk_whatsapp' (different channel).

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?

The description provides context by labeling it as 'High-impact' and advising to 'confirm the list before calling,' implying a precautionary usage guideline. However, it does not explicitly state when to use this tool versus alternatives like 'send_sms' for single messages or 'send_bulk_email' for email, though the bulk SMS purpose is clear.

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