Cancel Broadcast

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

With no annotations, the description bears the entire behavioral burden. It fully discloses the nuanced effects: queued broadcasts stop mid-send, already-sent emails are unaffected, scheduled broadcasts revert to draft, and sent broadcasts are immutable. This goes well beyond minimal requirements.

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 structured with purpose, exclusions, and when-to-use sections, and every sentence earns its place. It is front-loaded with the core purpose and avoids filler while still covering edge cases.

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 single-parameter mutation tool with no output schema, the description provides strong contextual completeness: purpose, target states, exclusions, and a sibling pointer. The only minor gap is not describing the cancellation response or confirming idempotency, but this is not critical 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% and already includes the broadcast ID/URL meaning and example. The tool description adds no extra detail about the parameter beyond what the input schema provides, so the baseline applicable score is correct.

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 clear verb+resource: cancel a queued or scheduled broadcast by ID or dashboard URL, with the explicit scope that it removes no broadcast. It distinguishes itself from remove-broadcast by name, so an agent can tell this tool apart from its closest sibling.

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 gives explicit 'NOT for' guidance, excludes drafts and sent broadcasts, and tells the agent to use remove-broadcast instead when removal is intended. It also defines a concise 'When to use' trigger matching common user phrasing like 'stop', 'cancel', or 'pause'.

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