meta_ad_insights

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

No annotations are provided, so the description carries the full burden. It discloses the output fields, which is useful, but does not mention authentication needs, rate limits, or explicitly state that it is a read-only operation. The word 'Get' implicitly indicates a safe read, and listing the return fields adds some transparency, but it stops short of richer behavioral 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 two sentences, front-loaded with the core purpose and followed by a concise list of output fields. There is no fluff or redundancy, and every clause adds value.

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 list the returned fields, which is good. However, it lacks context on scope (e.g., whether all ads in the account are returned for the date range), pagination behavior, or how it differs from adset/campaign insights. Given the straightforward nature of a read tool and schema coverage, it is minimally complete but not rich in guidance.

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%, so the parameters are already well-documented in the schema. The description adds no additional meaning about parameters like limit, adsetId, or campaignId, nor does it explain how filters interact. Baseline 3 is appropriate because the schema handles parameter semantics.

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 'Get performance insights for individual ads,' which is a specific verb (Get) and resource (individual ads). It lists the exact metrics returned (name, ad set, campaign, spend, impressions, clicks, conversions), distinguishing it from sibling tools like meta_campaign_insights and meta_adset_insights by explicitly targeting the ad level.

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 for ad-level insights through 'individual ads,' but does not explicitly state when to use this tool over alternatives. It lacks direct comparisons to meta_campaign_insights or meta_adset_insights, though the phrase 'individual ads' gives clear context that this is for granular ad data.

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