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

Annotations already mark this as mutating and non-idempotent, and the description adds meaningful context: it delivers real messages to every member, implying real-world side effects and scale. This goes beyond the schema/annotation signal, though it doesn't address auth or rate limits.

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?

Two short sentences that front-load the action and impact; the follow-up sentence 'This delivers real messages' earns its place by reinforcing side-effect severity. No filler.

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 three-parameter tool with fully described schema, the description covers action, timing, audience scope, and side effects. It could add a note about scheduling or return behavior, but nothing essential is missing 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?

Schema description coverage is 100%, so the baseline is 3; the description only echoes the list/audience distinction rather than adding format, constraints, or examples beyond the schema.

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?

Uses a specific verb ('send') and resource ('broadcast') plus the immediate-timing qualifier 'now', which distinguishes it from schedule_broadcast. It specifies the target population (every member of a list or audience), so the agent can tell it apart from send_message or broadcast creation.

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 phrase 'now' establishes immediate send context and the list/audience constraint narrows when to use it. It does not explicitly name alternatives such as schedule_broadcast or send_message_to_list, nor state when not to use them, 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.