search_slack

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

With no annotations provided, the description bears full burden. It mentions 'with your visibility' hinting at permission-based results and describes supported query syntax behavior. It does not disclose potential rate limits or pagination details, but the transparency about query capabilities is adequate.

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 two sentences long, front-loaded with the primary action, and each sentence adds meaningful information without redundancy. It is highly efficient and easy to parse.

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 tool has 2 parameters (one required), no output schema, and no annotations, the description provides adequate context for usage. It covers the query syntax and purpose but lacks information about the return format or behavior for empty results. However, it is reasonably complete for a search 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?

The schema has 0% description coverage, so the description must add meaning. It explains the 'query' parameter through examples of Slack syntax (e.g., 'in:#channel', 'from:@name'), adding value beyond the schema. However, it does not explain the 'limit' parameter or its constraints, leaving part of the parameter semantics unaddressed.

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 clearly states it searches Slack messages with a specific verb 'Search', identifies the resource 'Slack messages', and provides context about using Slack query syntax. It distinguishes itself by mentioning 'with your visibility' and gives use cases like finding past discussion, decisions, or context.

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 description explicitly says 'Call this to find past discussion, decisions, or context about a topic,' providing clear usage context. However, it does not differentiate from the sibling tool 'slack_channel_history' or specify when not to use this tool, but the guidance is still strong.

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