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

Annotations already declare this as a safe, read-only, idempotent operation. The description adds valuable behavioral context beyond that: the 40-item cap, the meaning of an empty list, the status values, and the condition that delivery counts appear only when the network reports them.

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 dense but front-loaded: it defines the resource and scope first, then lists return fields, then routes to sibling tools. Every clause contributes useful information without repetition.

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?

There is no output schema, but the description compensates by listing the key returned fields, the status enum, delivery count conditions, the result cap, and empty-list semantics. It gives an agent everything needed to call and interpret this tool correctly.

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 single workspaceId parameter has 100% schema description coverage, including its fallback behavior when the connection is tied to one workspace. The description only refers to 'the workspace' generally and does not add parameter-specific guidance beyond the schema, so 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 states a specific verb and resource ('List the broadcasts') and defines broadcasts precisely as 'one message sent to many contacts at once'. It also enumerates the fields returned, making the tool's scope distinguishable from siblings.

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 routes the agent to send_broadcast for sending a draft, cancel_broadcast for stopping a scheduled one, create_broadcast for creation, and list_sequences for automatic messages to one contact over time. The alternatives and conditions are named directly.

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