Import Ad Campaign Data from CSV

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

Annotations indicate non-readonly, non-destructive, non-idempotent behavior. The description adds that it persists data across tools, requires no API keys, and appends data on re-import with same connection_name. This provides useful behavioral context beyond annotations.

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 moderately long but well-structured with clear sections for HOW TO EXPORT and INPUT. Most sentences add value, though the HOW TO EXPORT section could be shifted to a separate guidance document to reduce length.

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 5 parameters, 100% schema coverage, and no output schema, the description effectively explains the import process and return summary content. It covers prerequisites (export steps), input options, and outcome (data available across other tools). Missing some details about required account_id but schema covers it.

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% so baseline is 3. The description does not add much detail beyond the schema descriptions already present (e.g., csv_path vs csv_content, connection_name default). It mentions the optionality of csv_path/csv_content and connection_name grouping, but schema already describes them adequately.

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 campaign + performance data from Google Ads or Meta Ads CSV exports, and mentions it activates all AdOps tools. This verb+resource specification distinguishes it from siblings like platform_connect (API-based) and ad_demo_seed (demo data).

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 provides explicit when-to-use (import real campaign data) and how-to-export instructions for both platforms. It doesn't explicitly mention when not to use it versus alternatives (e.g., platform_connect), but the context implies this is for CSV-based import only, which is clear enough.

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