slack_channel_history

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

No annotations provided, so description must fully convey behavioral traits. Only states 'oldest first' and 'recent messages'. Lacks details on read-only nature, whether threads are included, rate limits, or required permissions. Important for an agent to know if the operation is safe and what it returns.

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 concise sentences, front-loaded with key action and use cases. No fluff or redundant information. Examples are helpful and immediately convey context.

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?

Simple tool with 2 parameters and no output schema. Description covers main purpose but omits output format, pagination behavior, and whether metadata (e.g., timestamps) is included. Could be more complete for a tool used to 'catch up' by detailing what the result looks like.

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 covers 'channel' with a description, but 'limit' lacks explanation. Description adds no parameter details beyond schema. With 50% schema coverage, baseline is 3; description does not compensate by explaining parameter behavior (e.g., what 'limit' controls).

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?

Clearly states the tool fetches recent messages from one Slack channel, sorted oldest first. Provides concrete use cases (catching up on #eng, #standup, checking latest discussion). Distinguishes from 'search_slack' sibling by focusing on history retrieval.

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?

Explicitly suggests when to call: to catch up or check latest discussion. Does not explicitly exclude cases (e.g., searching for specific terms), but context clearly differentiates from search siblings. Could mention alternative tools like 'search_slack' for search scenarios.

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