Search Meta Ads

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

Annotations already indicate readOnlyHint false, but the description adds meaningful context: it discloses the paid nature of the underlying Actor and the side effect of storing normalized evidence. This goes beyond annotations, though it does not cover rate limits or authentication, which are less critical given the external API context.

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 only two sentences, front-loaded with the core purpose and followed by a key operational detail. Every word contributes, with no redundancy or filler.

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?

With no output schema, the description does not clarify what the tool returns, which is a notable gap. It does provide context about paid execution and evidence storage, which helps, but it lacks guidance on output shape and relationship to sibling tools, making it only moderately complete.

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 coverage is only 40%, and the description does little to compensate. It mentions 'by keywords and market,' which aligns with the queries and markets parameters, but it does not explain active_only, results_per_query, or the significance of deep beyond the schema's own description. The description adds marginal value over the schema.

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's function: 'Search public Meta Ad Library data by keywords and market.' This is a specific verb+resource+scope and distinguishes it from siblings like analyze_competitor_ads and get_market_evidence, which focus on analysis or retrieval of stored evidence.

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 implies usage by mentioning 'runs a paid Apify source Actor and stores normalized evidence for reuse,' hinting that this fetches fresh data for later retrieval. However, it does not explicitly state when to use this tool versus alternatives like get_market_evidence or analyze_competitor_ads, leaving the usage context implicit.

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