Account summary

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds what data is aggregated (status, budgets, serving issues, performance) but says nothing about cost, latency, rate limits, or whether campaign lists are paginated/capped — relevant for a broad aggregate call.

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?

A single front-loaded sentence leads with the key framing ('One-shot snapshot') and then enumerates the returned content with zero filler. Every clause earns its place.

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?

With no output schema, the description usefully enumerates the response contents (account status, campaigns with budgets and serving issues, per-campaign performance), which covers most of what an agent needs. Only the parameter bounds and limits on the aggregate are left implicit.

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 description coverage is 0%, so the description must compensate for the single integer parameter. It does add the semantic meaning ('last N days') and the default (7), which the schema lacks, but omits the documented 1–90 bounds, leaving the parameter only partially explained.

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 states a specific composite operation: an account snapshot bundling status, active campaigns with budgets/serving issues, and per-campaign performance. The 'one-shot snapshot' framing distinguishes it from granular siblings like list_campaigns and get_campaign, though no sibling is named explicitly.

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?

'One-shot snapshot' implies the tool should be used when a broad overview is wanted instead of many individual calls, which is useful implied guidance. However, it never states when to prefer this over alternatives such as get_insights or list_campaigns, nor any exclusions or prerequisites.

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