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

With no annotations, the description carries the full burden of behavioral disclosure, yet it reveals nothing about side effects, authentication needs, rate limits, result shape, or pagination behavior. The agent has no idea what 'Search' actually does operationally.

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?

While extremely short (one word), this is under-specification, not effective conciseness. The description does not earn its place because it adds no meaningful information and fails to capture essential details about the tool's purpose or behavior.

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 has three parameters, no output schema, no annotations, and a vast list of sibling search tools, this description is completely inadequate. It lacks any information about result types, scope of search, or relationship to similar tools, making it impossible for an agent to use 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 schema has 100% description coverage for all three parameters (trim, query, cursor), so the baseline is 3. The description itself adds no parameter information, but the schema already provides adequate definitions for each parameter.

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 is simply 'Search', which tautologically restates the tool name's 'search' component without specifying what entity or domain is being searched. It fails to distinguish this tool from numerous sibling search tools like scrapecreators_search, scrapecreators_search_ads, or scrapecreators_search_by_hashtag.

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?

There is no guidance on when to use this tool versus the many search-related siblings. The one-word description provides no context, prerequisites, or exclusions, leaving the agent to guess which search tool is appropriate.

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