Get Ad Account Insights

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

Annotations already indicate read-only and non-destructive behavior. The description adds significant value by enumerating the exact metrics returned (performance, cost, engagement, conversions, video, quality), which goes beyond the schema and annotations. It does not disclose any side effects or permission requirements, but the read-only annotation covers the main behavioral trait.

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 well-structured: a one-line purpose, a clear parameter list with explanations, and a bulleted list of return metric categories. While it is relatively long, the structure and front-loading of purpose make it easy to parse. Every section 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?

Given the tool's complexity (6 parameters, no output schema, many sibling tools), the description thoroughly covers all parameters and provides an exhaustive list of return metrics by category. It compensates for the lack of output schema by detailing response content. The description is complete for an agent to understand inputs, outputs, and scope.

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 description adds meaning beyond the input schema for ad_account_id (provides example format) and breakdowns (lists available options). For date_preset, schema already provides full enum. With schema coverage at 83%, the description compensates for the missing schema description on ad_account_id and enriches understanding of breakdowns.

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 explicitly states it 'Gets performance insights for a Meta ad account,' which is a clear and specific verb–resource pair. The tool name itself differentiates it from similar tools like meta_get_ad_insights and meta_get_campaign_insights, and the description reinforces this by detailing the 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 provides no guidance on when to use this tool versus alternatives like meta_get_ad_insights or meta_get_campaign_insights. It does not mention prerequisites, context, or exclusions. The usage is implied but not explicitly stated.

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