Create broadcast (draft)

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

Annotations only declare readOnlyHint=false, so the description carries real weight here and delivers the key trait: this creates a draft and does not send, which is exactly the behavioral distinction an agent needs before invoking. It adds the mutual-exclusivity constraint on audience params but says nothing about permissions, limits, or what happens to mediaAssetIds.

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?

Three tight sentences with the draft/not-send constraint front-loaded, followed by the audience rule and the routing hint. No filler and no restatement of the name or title.

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 the highest-risk aspects for this tool: the draft semantics, the audience exclusivity rule, and the handoff to send_broadcast. The nested filter object is given an example, which is helpful, but the definition is still silent on four parameters and there is no output schema to fill the gap.

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 0% across 7 parameters, so the description must compensate and only partly does: it explains segmentId, filter (with a concrete {minScore:50} example), and the format default of TEXT. The three required parameters (name, igAccountId, templateText) and mediaAssetIds (including its maxItems of 10) are left entirely undocumented.

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?

States a specific verb and resource ('Create a DRAFT broadcast') and immediately scopes it with '(does NOT send)', which separates it from send_broadcast and list_broadcasts in the sibling set. An agent can route to this tool without opening any schema.

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?

Gives explicit when-to-use routing ('Use send_broadcast to send it') and a hard selection rule for the audience ('Provide exactly one audience: segmentId OR filter'). It doesn't address how this differs from create_automation, which is a plausible confusion in this sibling set, so it stops short of a 5.

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