create_aibroadcast

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

Annotations indicate a write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that messages are sent to real recipients and are irreversible once delivered, providing behavioral context beyond annotations.

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 somewhat repetitive (e.g., 'Create AI-generated broadcast' appears both in title and text). It front-loads key info but could be more concise. The warning is helpful but adds length.

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 description covers purpose and a warning, but lacks details about return value (no output schema), rate limits, or cost implications. For a write tool sending messages, more completeness would be beneficial.

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?

The input schema describes each parameter (prompt, tone, source) with brief descriptions. The tool description adds no additional parameter-level meaning. With 100% schema coverage, 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 tool creates or schedules an AI-generated outbound message (SMS or WhatsApp). The title and content explicitly mention 'AI-generated broadcast', distinguishing it from non-AI broadcast tools like 'create_broadcast' among siblings.

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 implies usage for AI-driven broadcasts and includes a warning to confirm audience before sending, but it does not explicitly specify when to use this tool versus alternatives (e.g., create_broadcast for non-AI broadcasts). Usage context is implied but not explicit.

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