slack_search_messages

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

No annotations are provided, so the description must carry the burden. It merely says 'Search Slack messages' without revealing any behavioral traits like search scope (e.g., across all channels, time range) or limitations. This is minimal disclosure.

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 a single short sentence, achieving conciseness but sacrificing informativeness. It is not verbose but fails to earn its place due to lack of detail.

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?

For a search tool with no parameters and no output schema, the description is critically incomplete. It does not specify what is searched (all messages? recent?), how results are returned, or any constraints. The agent lacks adequate context to invoke 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 input schema has zero parameters, and schema coverage is 100%. Baseline for 0 parameters is 4, and the description does not need to explain parameters. However, it could have provided context about how the search works without parameters (e.g., default scope), but it does not.

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 'Search Slack messages' states a verb and resource, but is vague and does not distinguish from sibling tools like 'search_messages' or 'slack_read_channel_messages'. It lacks specificity about scope or search behavior.

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 such as 'search_messages' (general) or 'slack_list_channels'. The description gives no context or exclusions.

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