google_ads_create_conversion_action

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

The description discloses the write operation and return of a success message with conversion action ID and tag snippet, but does not mention permissions, rate limits, or idempotency. With no annotations, this is moderately transparent.

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 structured with Args, Returns, and Example sections, making it easy to parse. Though lengthy due to 9 parameters, it is appropriate and not unnecessarily verbose.

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 the complexity and presence of an output schema, the description covers all inputs and return value adequately. It lacks error handling or prerequisite details but is otherwise complete.

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 coverage, the description compensates fully by explaining every parameter in detail, including constraints (e.g., 'without hyphens' for customer_id, lookback windows) and examples. This adds significant meaning beyond the schema.

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 function 'Create a conversion action for tracking' and lists all parameters. It implicitly distinguishes from siblings like update and list by using 'create', but lacks explicit differentiation.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention when to use vs update or other creation tools, relying on the name alone.

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