send_quick_bulk_sms

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

No annotations provided, so description carries full burden. It discloses side effect 'indexes campaign id in session cache' and behavior of verify_sender. However, it does not mention destructive potential, idempotency, or cost implications of sending SMS.

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?

Organized with bullet points for parameters, front-loaded with purpose sentence. Efficient but includes redundant alias detail. Could be slightly more terse.

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?

Covers purpose, parameter constraints, return payload, and side effect. Missing prerequisites (e.g., registered sender_id) and safety context (cost, rate limits). Output schema exists but its content is not shown, so return info is vague.

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?

With 0% schema description coverage, the description adds critical meaning: max lengths for sender_id (11 chars) and message (460 chars), format for schedule_time, and alias relationship for recipients. These go well beyond the bare schema.

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 SMS to explicit phone numbers,' which is a specific verb and resource. It distinguishes from sibling tools like send_bulk_group_sms by specifying 'explicit phone numbers' versus groups.

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 versus alternatives (e.g., send_bulk_group_sms). The description provides parameter details but lacks when-not-to-use or prerequisite context.

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