send_broadcast

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

No annotations are provided, so the description carries the full burden. It explains the one-shot nature but does not disclose potential side effects, irreversibility, or rate limits. The phrase 'immediately schedule it to send' could be clearer about actual send timing.

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 brief and to the point, two sentences without extraneous information. It front-loads the primary purpose and includes critical usage notes.

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 tool's complexity (13 parameters, no output schema), the description covers key constraints but omits details about return values, error scenarios, and the 'filter' parameter not in the schema. It could be more complete.

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 description adds meaningful context beyond the schema, explaining the mutually exclusive audience selection and the html/templateSlug requirement. However, it mentions 'fully-qualified filter' which is not present in the input schema, causing some confusion.

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 it is a one-shot broadcast that creates and immediately schedules a campaign. It distinguishes itself from siblings like create_campaign and schedule_campaign by emphasizing the combined action.

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 specifies that one of audienceId, segmentId, topicId, or filter must be provided, and either html or templateSlug. It implies immediate sending but does not explicitly contrast with alternatives like creating and scheduling separately.

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