slack_search_messages

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

No annotations provided, so description carries full burden. It clearly discloses search scope (locally-cached channels) and method (substring matching). However, it does not mention potential staleness of cache or performance characteristics, which would add transparency.

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?

Single sentence with no redundancy. Every word adds value: specifies resource, scope, and method. 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 no output schema and low complexity, description covers key aspects (what, where, how). Missing mention of cache freshness as a limitation, but overall sufficient for an agent to understand basic functionality.

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?

Input schema is empty (0 parameters), so schema coverage is 100%. Per guidelines, baseline is 3. Description does not need to add parameter info, but also does not provide any additional context about input expectations.

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?

Description clearly states verb ('Searches'), resource ('Slack messages'), scope ('across locally-cached channels'), and method ('full-text substring matching'). This distinguishes it from sibling tools like slack_read_channel_messages (reads specific channel) and slack_list_channels (lists channels).

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 when-to-use or when-not-to-use guidance. The description implies usage for searching messages across channels but doesn't compare to alternatives or mention prerequisites like cache availability. Without annotations, this is adequate but not explicit.

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