slack_read_channel_messages

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

With no annotations, the description carries the full burden, and it does add one valuable behavioral fact: reads happen through the Slack Desktop app signed in on this Mac. It does not disclose how many messages are returned, whether unread state or pagination applies, or what happens if the app is closed — and the visible text is cut off before any of that.

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?

Short and front-loaded with the verb and resource, but the definition ends mid-sentence ("(its o..."), so it is incomplete rather than concise. The essential information arrives first, which limits the damage.

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?

With no annotations, no output schema, and no parameters, the description is the sole source of behavioral detail and it is truncated. It never says how many messages come back, what they contain, or how failures (app signed out, no channel) are surfaced, leaving real gaps for an agent.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The mention of "recent messages" is the only implicit scoping hint, but no arguments exist to document.

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 ("Reads") and resource ("recent messages from a Slack channel or DM"), which distinguishes it from write-oriented siblings like send_message. However, the text is truncated mid-sentence and never names the sibling it should be preferred over (e.g. slack_search_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 explicit guidance on when to use this versus slack_search_messages or slack_list_channels, nor any prerequisite (app must be running and authenticated) stated as a condition. The only implicit cue is "recent messages", which leaves recency/window selection to inference.

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