google_ads_conversions_create

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

With no annotations, the description carries full burden. It discloses that the tool is 'Mutating', persists the action with 'status ENABLED by default', returns a resource_name, and is reversible via specific methods. Also reveals constraints like name length and default category, showing substantial transparency.

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?

Four dense sentences, each earning its place: purpose, return value, mutating/persistence, reversibility, constraints, and alternative tool. Front-loaded with the primary action, no fluff.

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?

For an 8-parameter create tool with no output schema, the description fully covers what the tool does, what it returns, its side effects, defaults, and pointer to update. Combined with rich schema descriptions, this is complete for an agent to invoke correctly.

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 100%, so baseline is 3. The description adds a couple of defaults (status, category) but those are already in the schema. It does not meaningfully enhance parameter semantics beyond what the schema already states, so no higher score.

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 opens with 'Create a new Google Ads conversion action' — a specific verb and resource. It clearly distinguishes from siblings by explicitly mentioning google_ads_conversions_update for updates and noting reversibility via remove, making the purpose unambiguous.

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 explicit when-to-use guidance: use for creating new conversion actions, and for updating existing ones 'use google_ads_conversions_update'. Also states lifecycle/reversibility options (update with REMOVED or remove), giving clear usage context.

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