meta_ads_analysis_audience

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

Discloses read-only behavior and describes output structure (rows with metrics, recommendations). Lacks mention of Graph API quota costs, but parameter schema covers that for period.

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?

Three sentences: purpose, output details, usage guidance. No wasted words, front-loaded with core 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?

Covers purpose, output, usage context, and alternative tool. No output schema but description sufficiently details return fields. Lacks error handling or quota notes, but adequate for tool 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?

Schema coverage is 100% with good parameter descriptions; description adds no additional parameter semantics beyond what schema provides.

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?

Description states specific action 'scores delivery efficiency' across age × gender segments, clearly differentiating from sibling tool meta_ads_insights_breakdown which provides raw breakdown numbers.

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 before adjusting targeting' and provides alternative 'for raw breakdown numbers use meta_ads_insights_breakdown with breakdown='age,gender'', offering clear when-to-use and when-not-to-use guidance.

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