Send Message Sequence

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

The description adds useful behavioral context beyond the annotations: steps are sent in order, each step can contain messages, actions, quick replies, and delays. However, it does not explicitly state that this sends live messages to a real subscriber or that tag/field actions mutate subscriber data, and the annotations only say the operation is not read-only and not destructive.

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 sentences with no fluff: the first states the primary action, the second summarizes step composition, and the third gives a concrete use case. It is front-loaded and every sentence earns its place.

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 tool is complex, but the rich input schema already covers parameter constraints and structure. The description provides a sufficient high-level model of how the sequence behaves. It could mention response/error behavior, but since there is no output schema, the absence is not a critical gap for correct invocation.

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 has full 100% description coverage, so the schema already documents all parameters and their meanings. The description mentions messages, actions, quick replies, and delay at a high level, which aligns with the schema but does not add new parameter-level detail. 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 action ('Send a multi-step message sequence to a subscriber') and names the main resource (subscriber and steps). It communicates the tool's purpose well and sets it apart from simpler send tools by emphasizing multi-step composition, but it does not explicitly name sibling alternatives like manychat_send_flow or manychat_send_content.

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 says 'Use this to create automated conversation flows programmatically,' which gives a clear when-to-use context. It does not provide explicit exclusions or compare itself to sibling tools, but the use case is specific enough for an agent to route to this tool.

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