keyword_search

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

Discloses key behavioral traits beyond basic function: polling until completion, truncation of oversized responses with a truncated flag, and the results_pending status. Since no annotations are provided, this fully covers the operation's side effects and return handling.

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?

Purpose is front-loaded in the first sentence, followed by crucial behavioral notes. The query guidance is lengthy but earns its place by preventing misuse. No filler or redundancy.

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 complexity of a cross-platform search tool with polling and possible truncation, the description thoroughly sets expectations for return states and directs users to sibling tools for complete data. Adequate even without an output schema.

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?

Although the schema covers all parameters, the description significantly enhances the query parameter by explaining token-OR matching, boolean operators (AND, OR, NOT), quoting, and providing a concrete example. This goes far beyond the schema's minimal descriptions.

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 states a specific verb ('Create') and resource ('keyword/hashtag search') across multiple social media platforms, making the tool's purpose clear. It also distinguishes itself from sibling tools like get_keyword_search and get_keyword_search_posts by clarifying that it creates and polls the search, while those retrieve results.

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?

Provides explicit when-to-use guidance: for truncated responses, use get_keyword_search_posts; for results_pending status, use get_keyword_search. Also recommends boolean syntax and focused searches over broad queries, clearly steering usage behavior.

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