Search Meta Ad Library

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by describing the tool as a transparency tool. It adds context by noting that a valid access token is required but not ad account ownership, and describes the return values.

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 well-organized with a clear opening sentence followed by a structured parameter list. It is concise but includes all necessary details; could be slightly shorter but remains efficient.

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 no output schema, the description summarizes what the tool returns (ad creatives, spend ranges, impressions, etc.), which is sufficient for an agent. The note about the access token requirement adds useful context. With 10 parameters, the description covers key aspects adequately.

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 description enhances the 60% schema coverage by listing all parameters with concise explanations, including enum values and defaults. It clarifies the required country codes and optional filters like date range and pagination, adding meaning beyond 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 explicitly states it searches the Meta Ad Library for ads from any advertiser, clearly identifying it as a transparency tool without requiring ad account access. This distinguishes it from sibling tools that typically require ad account credentials.

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 clarifies that no ad account is needed, providing a key differentiator from many sibling tools that require ad account access. It outlines parameters but does not explicitly name alternative tools or state when not to use this tool.

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