Get Ad Set Insights

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context through parameter usage instructions, but does not disclose side effects, rate limits, or data freshness beyond the annotations. The added value is minimal, resulting in a score of 3.

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 concise and well-structured, with a clear heading followed by a bulleted parameter list. It is front-loaded with the main purpose and contains no extraneous information. Every sentence serves a purpose.

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?

Without an output schema, the description should clarify return format or data structure. It mentions response_format in the schema (markdown/json) but not in the description. It also lacks details on pagination, result limits, or error handling, leaving gaps for a complex 8-parameter tool.

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 low (38%). The description compensates by explaining the purpose of each parameter (e.g., 'Ad account ID (use for all ad sets)', 'Custom date range YYYY-MM-DD') and clarifying that breakdowns include dimensions like age, gender, country. This adds significant meaning beyond the schema's property names and enums.

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 'Gets performance insights for ad sets' with a specific verb and resource. It distinguishes from sibling tools like meta_get_ad_insights and meta_get_campaign_insights by focusing on ad sets. The parameter guidance further clarifies the tool's scope.

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 advises to provide ad_account_id or campaign_id or adset_id, offering basic usage guidance. However, it fails to explicitly differentiate when to use this tool over other insight tools like meta_get_ad_insights or meta_get_account_insights, lacking exclusion criteria or alternative recommendations.

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