Meta Ads Search

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

No annotations are provided, so the description carries full behavioral disclosure burden. 'Search' implies a read-only operation, but the description says nothing about authentication needs, result limits, pagination, or what kinds of ad data are returned.

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 definition is short and front-loads the core search action. The second sentence, 'Discover social media advertising strategies and creative campaigns,' is vague marketing framing rather than actionable guidance, so it does not fully 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 simple two-parameter search, the description covers the basic purpose and inputs, but it omits usage distinctions from related ad-search siblings and does not explain return behavior despite having no output schema or annotations.

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 usefully maps the two inputs to company domain or name. However, it does not clarify whether either parameter is sufficient, whether both are required, or what format each should take.

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 gives a specific verb and resource: search Meta (Facebook/Instagram) Ads, with the input basis (company domain or name). It clearly differentiates from search_google_ads by naming the ad platform, though it does not explicitly mention sibling alternatives.

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?

It states the search basis but provides no guidance on when to use this tool versus search_google_ads, search_b2b_ads, or get_b2b_ad_details. There are no prerequisites, exclusions, or conditions for choosing this tool.

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