meta_ads_insights_report

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

No annotations provided, but the description declares 'Read-only' and discloses that longer windows and finer levels consume more Graph API quota, giving the agent important behavioral context beyond a simple read-only flag.

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 concise sentences for the core purpose, followed by a usage note. No redundant information; every sentence adds value. Front-loaded with key facts.

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?

The description covers the tool's purpose, input parameters, and behavioral notes (read-only, quota impact). Returns a list of metrics, though it could mention output structure or pagination. Overall adequate for a read-only report 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 coverage is 100%, so baseline is 3. The description adds value by listing the returned metrics (impressions, spend, etc.) and explaining the impact of period and level on API quota, which goes beyond the schema definitions.

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 'Pulls raw delivery metrics from Meta Graph API Insights' with a list of specific metrics and aggregation levels, distinguishing it from the sibling 'meta_ads_analysis_performance' by explicitly contrasting raw vs. interpreted findings.

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?

Explicitly states 'Use this when you need raw metrics; for interpreted findings (period comparison, outlier callouts) use meta_ads_analysis_performance instead.' Provides clear guidance on when to use and when not to, with a direct alternative.

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