create_broadcast

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

The description explicitly labels the tool as 'WRITE', mentions it sends or schedules outbound messages to real recipients, and warns about irreversibility. This adds behavioral context beyond the annotations (which only indicate readOnlyHint=false and destructiveHint=false). No contradictions with 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 short but somewhat repetitive (e.g., 'Create a new broadcast message' appears twice). The use of emoji and HTTP method is helpful but could be more streamlined.

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 the main purpose and irreversibility but misses details about scheduling, segmentation, MMS, and return values. Given no output schema, it should hint at what the response contains.

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% with descriptive parameter names and some descriptions (e.g., 'SMS message content', 'Name of the broadcast'). The tool description does not add additional parameter semantics beyond what the schema provides, meeting the baseline.

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 a broadcast message for SMS/WhatsApp. It distinguishes itself as a broadcast tool, but does not explicitly differentiate from siblings like 'create_campaign' or 'create_a_new_message'.

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 includes a warning about irreversibility ('Not reversible once delivered — confirm the audience first.'), providing some usage guidance. However, it does not specify when to use this tool over alternatives like 'create_aibroadcast' or mention prerequisites.

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