ecommerce_google_ads_integration

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention side effects, authentication requirements, rate limits, or the fact that dispatching campaigns or tracking conversions likely sends data to an external Google Ads system. This is a significant transparency gap for a potentially state-changing integration tool.

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 short sentence, so it is concise, but the phrasing is awkward and compressed to the point of ambiguity. It would be more effective if it led with a clear verb and then separated the two responsibilities.

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 tool has four parameters, two nested objects, two enum-based action values, and no output schema, yet the description provides almost no operational context. An agent needs to understand when to use each action, what payload data is required, and what happens after invocation, none of which is conveyed.

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 undocumented parameters. It loosely references 'Campaign Payload' and 'offline conversion tracking,' which faintly echo campaignPayload and action=track_offline_conversion, but it does not explain required parameters like platform and action, nor the semantics of conversionData or campaignPayload fields.

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 identifies the domain (Google Ads) and two broad capabilities (campaign payload dispatch, offline conversion tracking) that map to the action enum, so it is not a pure tautology. However, 'Integrate Google Ads Campaign Payload dispatcher' is an awkward noun phrase and does not state a clear verb or resource, leaving ambiguity about what action is actually performed.

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?

There is no guidance on when to use this tool versus alternatives, nor any explanation of when to choose dispatch_campaign versus track_offline_conversion. The only contextual hint is the platform list, which does not help an agent decide if this tool is appropriate for a given task.

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