slack_delete_scheduled_message

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

Annotations are absent, so the description must convey behavioral details. It mentions routing and authentication scope but fails to disclose that deletion is irreversible, required permissions, or side effects. This is minimally informative.

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 short (two sentences) and avoids verbosity, but the structure is suboptimal—routing details take precedence over functional clarity. It is concise but could be better organized.

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?

Given the complexity of Slack's API and the generic 'arguments' parameter, the description lacks crucial input structure details. The output schema exists but is not referenced. The description is incomplete for an agent to use 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 parameter 'arguments' has 0% schema coverage. The description only says it's a 'JSON string of arguments' without specifying expected keys (e.g., channel, scheduled_message_id). This is a critical gap for proper invocation.

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 explicitly states it is for deleting a scheduled message in Slack, naming both the connector operation and platform tool. This clearly distinguishes it from siblings like slack_delete_message (deletes regular messages) and slack_list_scheduled_messages (lists scheduled 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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or when not to use it. The description is purely factual without context for decision-making.

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