get_ad_performance

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

No annotations are provided, so the description must disclose behavioral expectations. It only states the operation and metric names; it does not mention data freshness, sorting, row limits, filtering behavior, or any side effects/requirements beyond the operation name.

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 a single, focused sentence that front-loads the core purpose and lists key result dimensions. No wasted 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?

An output schema is present, so return values don't need description. However, the tool has six parameters with three required but no guidance on required inputs or how to combine filters; the description is adequate for a simple read but leaves contextual gaps.

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 does not explain any parameters. The schema covers some parameters (customer_id, campaign_id, row_limit) but leaves start_date, end_date, and account undescribed; the description does not compensate or clarify date formats or account usage.

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 ad-level performance and specifies the metrics included (headlines, descriptions, CTR, conversions), distinguishing it from sibling campaign- and keyword-level tools.

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 it should be used when ad-level metrics are needed, but it does not explicitly compare to alternatives like get_campaign_performance or get_keyword_performance, nor state when not to use it.

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