send_broadcast

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false (not destructive). The description adds the timing behavior (immediate vs scheduled) but no additional behavioral context such as rate limits, required permissions, or side effects beyond what annotations convey.

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 a single, efficient sentence. Every word is necessary and contributes to understanding the tool's core function and the key parameter behavior.

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 simple, two-parameter tool with no output schema and straightforward behavior, the description covers the main use cases. However, it does not clarify that a broadcast must already exist (via create_broadcast) or define what a broadcast entails, which could aid completeness.

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 100%; both parameters are already described in the schema. The description merely rephrases the schema's prompt to omit scheduledAt for immediate sending, adding no deeper semantic meaning.

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 'Send a broadcast now, or schedule it for later.' It uses a specific verb (send) and resource (broadcast), and the distinction from siblings like send_email (single email) or send_batch_emails (custom batch) is evident from the name and context.

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 provides guidance on when to use immediate vs scheduled sending via the scheduledAt parameter. However, it does not explicitly state when not to use this tool or mention alternatives for creating or updating broadcasts, which are available as siblings.

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