slack_smart_search

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds that it requires Vectorize + Workers AI and mentions the free tier limit of 10 calls/month, upgrading to Pro. This provides useful context beyond the annotations without contradicting them.

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 concise, with three sentences that cover purpose, return values, and limitations/pricing. It is front-loaded and avoids unnecessary repetition. Each sentence adds value, though the pricing detail could be considered extraneous for some agents.

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 is read-only with comprehensive annotations and 100% schema coverage, the description provides adequate context. It explains the hybrid search approach and limitations. However, without an output schema, the description could clarify the return format in more detail.

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 covers 100% of parameters with descriptions. The tool description adds nuance for the query parameter ('Natural language or keyword query') and notes the days_back limit (max 90 on Pro+, 7 on Free), which provides additional context beyond the schema.

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 defines the tool as a 'Semantic + lexical hybrid search' across Slack history, specifying it returns ranked results with relevance scores, channel context, thread context, and matched terms. It distinguishes itself from siblings like slack_search_messages by mentioning the hybrid approach and hosted nature.

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 states the tool is for searching indexed Slack history and mentions hosted-only requirements and pricing. However, it does not explicitly indicate when to use this tool over alternatives like slack_search_messages, nor does it provide conditions for when not to use it.

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