keyword_search

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

The description discloses the polling behavior until search complete, which is a key behavioral trait. However, without annotations, it lacks details on authorization needs, rate limits, or side effects; for a search tool this is adequate but not thorough.

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 consists of two concise sentences that front-load the main verb and purpose. Every sentence adds value without unnecessary words or repetition.

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?

Without an output schema, the description only vaguely says 'returns the full results' without specifying structure or format. For a polling search tool with sibling get_keyword_search endpoints, more detail on output is needed for completeness.

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?

All 5 parameters have descriptions in the input schema (100% coverage). The tool description adds no additional parameter semantics beyond what the schema already provides, so baseline of 3 is appropriate.

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 the tool creates a keyword/hashtag search across multiple social media platforms, listing examples. It distinguishes from sibling tools like user_search and expert_search by specifying the search type.

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 mentions polling behavior and return of full results, but does not explicitly state when to use this tool over alternatives like user_search or expert_search. No when-not-to-use or prerequisite info is provided.

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