Get Ad Insights

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by enumerating the metrics returned (impressions, clicks, spend, etc.), but it does not disclose pagination behavior, rate limits, or the output structure. This is acceptable given the read-only annotation, but the addition is not extensive.

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 a single sentence that directly states the tool's function and primary return values. It is front-loaded with the key action and resource, with no wasted words.

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 partially covers return values by listing examples of metrics, but it does not describe the output format or how results are organized. It also does not mention time_range handling or that insights are at the ad level relative to other scopes. Given 8 parameters and a sibling set with similar tools, more contextual detail would improve completeness, but the schema covers parameter specifics.

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 input schema has 100% coverage for all 8 parameters, so baseline is 3. The description's mention of metrics like impressions and clicks overlaps with the default value of the 'fields' parameter but does not add new meaning. The phrase 'by ID' aligns with the required ad_id parameter but adds no extra 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 the tool gets performance insights for a specific ad by ID, which distinguishes it from account-, campaign-, and adset-level insight tools. It also lists key metrics returned, reinforcing the tool's purpose. However, it does not explicitly name sibling tools for differentiation.

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 use for ad-level performance analysis by saying 'for a specific ad by ID', but it does not explicitly state when to use this tool versus get_account_insights or get_campaign_insights. No exclusions or alternative recommendations are provided, so usage guidance is implied but not explicit.

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