delete_scheduled_message

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose a key constraint: the scheduled message must be canceled 'before it is sent,' and the destructive nature is apparent from 'Cancel/delete.' However, it does not mention permissions, what happens if the message was already sent, or whether the operation is reversible.

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 that front-loads the action and constraint. Every word earns its place and there is no filler or redundancy.

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 fully described schema and no output schema, the description plus schema provides enough information for an agent to invoke it correctly. The only minor gap is that it does not mention how to obtain the scheduled_message_id or the behavior if the message is already sent.

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 already documents both required parameters with meaningful descriptions: 'Channel ID the message was scheduled for' and 'Scheduled message ID to cancel.' With 100% schema description coverage, the tool description adds no additional parameter semantics, so a 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 uses explicit action verbs 'Cancel/delete' and names the precise resource 'a scheduled message' with the temporal qualifier 'before it is sent.' This clearly distinguishes it from the sibling delete_message tool, which targets already-sent messages.

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 'before it is sent' provides a clear context for when the tool applies and sets the boundary that the message must not have been delivered. It does not explicitly name alternatives or state when not to use it, but the scheduled-message resource makes the intended use case clear enough.

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