meta_ads_ad_performance

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

Explicitly labels the tool as 'Read-only', which is a useful safety trait given no annotations are provided. However, it offers no details on return format, metrics, date ranges, or API limitations, leaving significant behavioral ambiguity.

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?

Extremely concise with the critical safety qualifier 'Read-only' placed first, followed by a clear action statement. No filler words; every element contributes to immediate comprehension.

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 has four parameters, no output schema, and no annotations, the description is too sparse. It fails to specify what performance metrics are returned, how date_preset affects results, whether ad_account_id is necessary, or how this differs from performance_trend, leaving agents to guess critical execution context.

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 has 0% description coverage, and the description only explains ad_id via 'by ID'. The other three parameters (date_preset, ad_account_id, advertiser_request) are left completely unspecified, so the description fails to compensate for the schema's lack of semantics.

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?

Clearly states it fetches performance data for a single ad specified by ID. The phrase 'one ad by ID' differentiates it from sibling tools like performance_trend, which likely cover multiple ads or periods.

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?

Provides no guidance on when to use this tool versus alternatives such as meta_ads_performance_trend or meta_ads_account_summary. The description implies single-ad lookups but does not state exclusions or scenarios where siblings are preferred.

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