Import Ad Campaign Data from CSV

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

Discloses key behaviors: re-importing with the same connection_name appends data, and returns a summary with campaigns_imported, metrics_imported, warnings, and connection id. Annotations provide no hints, so the description carries the full burden.

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?

Well-structured with clear sections for purpose, export instructions, and input details. The HOW TO EXPORT section is detailed but practical; overall length is justified given the complexity of supported platforms and input options.

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?

Covers all aspects: purpose, required inputs, behavior on re-import, return values, and platform-specific export steps. No output schema exists, so the description adequately explains the return summary.

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 coverage is 100% with descriptions for all 5 parameters. The description adds significant value by explaining the preference for csv_path for large exports, the default for connection_name, and the purpose of account_id, going beyond schema details.

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 imports real campaign data from Google Ads or Meta Ads CSV exports. It distinguishes from siblings like ad_demo_seed (demo data) and platform_connect (API) by emphasizing no API keys needed.

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 context on when to use (CSV exports, no API) and includes step-by-step export instructions for both platforms. However, it does not explicitly compare with alternative import methods like platform_connect or ad_demo_seed.

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