meta_account_overview

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

No annotations are provided, so the description carries the full burden. It discloses the output metrics and optional breakdown dimension, and the verb 'Get' implies a read operation. However, it does not detail return structure, pagination, or any constraints like rate limits or data freshness, leaving some behavioral aspects unspecified.

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 purpose, and includes no redundant information. It is concise while covering the essential functions and optional breakdown.

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?

Given the lack of an output schema and annotations, the description lists key metrics and parameters, providing a clear picture of what the tool does. It falls short of fully distinguishing sibling tools and detailing output structure, but for a straightforward overview tool it is reasonably complete.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds little beyond the schema—it restates the optional breakdown and date range but does not provide extra context on parameter formats or relationships beyond what the schema already specifies.

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 retrieves a high-level performance overview for a Meta ad account with specific metrics (spend, impressions, clicks, CTR, CPC, CPM, conversions). The account-level scope distinguishes it from sibling tools like meta_campaign_insights or meta_adset_insights.

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 implies usage for account-level overviews and provides date range and breakdown context, but it does not explicitly mention when to use this tool over alternatives (e.g., campaign/adset/ad insights) or state exclusions. The usage guidance is implicit rather than explicit.

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