meta_ads_insights_report

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

The description states it is read-only, implying no destructive behavior. It describes the output rows with specific metrics, but does not explicitly mention quota costs or other side effects beyond what's in the parameter descriptions. Given no annotations, this is sufficient but not exhaustive.

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 action and output. Every sentence serves a purpose: describing function, listing returned metrics, stating read-only nature, and providing usage guidance. No unnecessary 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?

The tool lacks an output schema, so the description compensates by listing the exact metrics returned. It specifies aggregation levels and read-only nature. It does not cover pagination or limits, but for a reporting tool with 4 parameters, it provides sufficient completeness for an agent to select and use it appropriately.

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 the parameters are well-documented. The description adds context beyond the schema by enumerating the returned metrics and explaining the trade-off of longer windows consuming more quota (though this is in the schema for 'period'). This adds moderate value.

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 pulls raw delivery metrics from Meta Graph API Insights for a campaign or whole account, explicitly naming the metrics returned and aggregation levels. It distinguishes itself from the sibling tool meta_ads_analysis_performance by stating its purpose for raw metrics 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?

The description explicitly advises when to use this tool ('when you need raw metrics') and provides an alternative for interpreted findings ('meta_ads_analysis_performance'). It also declares the tool as read-only, setting clear context for invocation.

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