get_ad_performance

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds a list of returned fields, which provides some behavioral context but lacks details like pagination, data freshness, or permissions.

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?

Two sentences succinctly state the purpose and return values. Front-loaded with the key action and resource. No redundant or extraneous information.

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?

The output schema likely documents return values, so that aspect is covered. However, the description omits parameter details and usage context, making the tool definition incomplete for proper invocation. Moderate complexity with three parameters but no guidance.

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?

With 0% schema description coverage, the description must explain parameters but does not. It fails to mention that customer_id, date_range_start, and date_range_end are optional or how they affect results (e.g., filtering by customer or date range).

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 data, listing specific metrics. This distinguishes it from sibling tools like get_campaign_performance or get_keyword_performance, which operate at different levels.

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?

No guidance on when to use this tool versus alternatives such as get_asset_performance or get_detailed_asset_performance. The description does not indicate prerequisites, limitations, or context for selecting this tool among many performance gatherers.

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