B2B Ads Search

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

No annotations are provided, so the description must carry the full behavioral burden. 'Search' implies a read-only operation, but there is no mention of permissions, rate limits, return format, or whether the operation is safe. The description adds no concrete behavioral traits beyond the implied read nature.

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 first sentence is efficient and front-loaded with the key purpose. The second sentence ('Analyze business-to-business advertising campaigns and professional marketing strategies') is vague filler that restates the obvious and does not earn its place.

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?

For a search tool with no annotations and no output schema, the description should provide more context. It lacks usage guidance relative to siblings, parameter details, and any indication of return values. The definition is functional but incomplete for an agent to invoke it confidently.

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 0%, so the description must compensate. It does map the two parameters to 'company's domain or name', giving semantic meaning to company_domain and company_name. However, it omits format details, requiredness, or whether one parameter can be used alone, leaving significant gaps.

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 states a specific verb (search) and resource (B2B Ads), and clarifies the query basis (company domain or name). However, it does not differentiate this tool from siblings like search_google_ads, search_meta_ads, or get_b2b_ad_details, leaving ambiguity about its unique scope.

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 explicit guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. The description implies it is for searching B2B ads, but stops short of outlining when a user should choose this over similar search tools.

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