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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It offers no information about what the tool returns, whether it is read-only, any rate limits, or other behavioral traits. The bare phrase 'Advertiser Search' reveals nothing about side effects or output.

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 extremely concise, but it is under-specified rather than efficient. A two-word noun phrase does not earn its place because it conveys no actionable information and fails to serve the agent's needs.

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?

Despite having a simple schema and no output schema, the tool operates in a crowded space of sibling tools. The description is hopelessly incomplete—it doesn't even state the tool's basic function, let alone differentiate it from similar tools or clarify return values or search scope.

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?

Schema description coverage is 100% since the 'query' parameter has a description ('The query to search for'), so the baseline is 3. However, the tool description adds no extra meaning beyond this generic schema text; the nature of the query (e.g., advertiser name, ID) remains unspecified.

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 'Advertiser Search' is a noun phrase that simply restates the tool name (scrapecreators_advertiser_search). There is no verb or resource to specify what action is performed, and it fails to distinguish this from many sibling search tools like scrapecreators_search_ads or scrapecreators_search_for_companies.

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 guidance is provided on when to use this tool versus alternatives. With a sibling list containing multiple search-related tools (search, search_ads, search_for_companies, etc.), the absence of any usage context makes it impossible for an agent to select this tool correctly.

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