get_adset_insights

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

No annotations are provided, so the description must carry the burden. It only says 'Pull performance metrics' with no details on pagination, rate limits, authorization requirements, or any side effects. The scope 'ONE ad set' is clear but minimal 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?

Two sentences, no filler. Front-loaded with verb 'Pull' and immediately specifies scope 'ONE ad set'. Every word earns 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?

Tool has 10 parameters, no output schema, no annotations. The description is too brief: it does not explain the return format, default time range, or handle pagination, which are essential for a data-fetching tool with such complexity.

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?

Input schema has 10 parameters with 70% coverage. The description does not add any parameter-specific meaning beyond the schema; it only references get_campaign_insights for fields/breakdowns. With high schema coverage, the baseline is adequate.

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?

Clearly states 'Pull performance metrics for ONE ad set', distinguishing from sibling tools like get_ad_insights (ad-level) and get_campaign_insights (campaign-level). The reference to similar fields/breakdowns reinforces purpose.

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 says 'ONE ad set' indicating when to use, and references get_campaign_insights for comparable fields. However, it does not explicitly state when not to use (e.g., for multiple ads) or mention alternatives like get_ad_insights.

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