slack_list_scheduled

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two useful behavioral facts beyond that: results are ordered soonest-first and pagination is cursor-based per page. It does not say whether results are scoped to the required workspace or span all workspaces.

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, front-loaded with what the tool returns and the ordering, with pagination in the trailing clause. No filler, though the line break inside the description is gratuitous and the sentence is slightly fragmented.

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?

An output schema exists, so return shape need not be described, and the read-only safety profile comes from annotations. What remains missing is a statement of how the required workspace parameter scopes the listing and what channel_id filters, which matters for a four-parameter tool.

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 0%, so the description must carry the parameter burden. It explains only the cursor, and usefully so (the API names it next_cursor, so the mapping avoids a wrong guess). The required 'workspace' parameter and the 'channel_id' and 'limit' parameters get no semantic explanation at all.

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?

States a specific verb+resource: lists the caller's scheduled-but-unsent messages, and even names the underlying API method (chat.scheduledMessages.list). This implicitly separates it from slack_schedule_message and slack_cancel_scheduled, though no sibling is named explicitly.

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 pagination instruction ('Pass next_cursor as cursor for the next page') gives real operational guidance, but there is no statement of when to use this versus slack_cancel_scheduled or slack_schedule_message, and no prerequisites are mentioned.

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