send_broadcast

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly discloses that the action cannot be undone and that it emails every contact in the segment, which are critical non-obvious behaviors. It does not cover permissions, rate limits, or response format, but the most important side effects are explicit.

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 sentences with no filler. The core action is front-loaded, and the warning plus prerequisite are included without redundancy.

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?

For a two-parameter tool with no output schema and no annotations, the description covers the essential operational aspects: purpose, scheduling, scope, irreversibility, and the recommended alternative. The only notable gap is that the required id is not explicitly defined, but it is strongly implied by context.

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 schema documents scheduled_at as an ISO 8601 timestamp and mentions 'omit to send now'; the description reinforces this scheduling behavior. However, the required id parameter is undocumented in both the schema and the description beyond implying it is the broadcast/campaign identifier. With only 50% schema description coverage, the description only partially compensates.

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 states a precise verb and resource: 'Send a campaign now, or schedule it with scheduled_at.' It also clarifies scope by noting it mails every contact in the segment, which distinguishes it from preview_broadcast and list_broadcasts.

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?

It explicitly gives both usage modes (send now or schedule) and warns to run preview_broadcast first. The irreversible consequence is stated, providing clear guidance on when to use this tool versus previewing first.

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