ghl_ad_google_conversion_delete

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

Annotations already indicate destructiveHint: true and readOnlyHint: false. The description adds the endpoint and OAuth scopes but does not elaborate on additional behavioral traits like irreversibility, required permissions beyond scopes, or rate limits. It does not contradict 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 brief and includes essential information (action, resource, endpoint, scopes). It could be slightly more structured but is efficient with no unnecessary words.

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 a delete operation without an output schema, the description is reasonably complete: it specifies the action, resource, identifier, and endpoint. Annotations cover the destructive nature. It could mention that it is irreversible, but that is implied by destructiveHint: true.

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 the input schema fully documents the three parameters (isDraft, locationId, conversionId). The description does not add any semantic details beyond the schema, so a baseline score of 3 is appropriate.

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 action ('Delete') and the resource ('a Google Ads conversion action by ID'). It distinguishes itself from sibling delete tools (e.g., ghl_ad_google_account_delete, ghl_ad_google_segment_delete) by specifying the exact resource type.

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 no guidance on when to use this tool versus alternatives such as ghl_ad_google_conversion_upsert or other delete tools. It does not mention prerequisites, when not to use, or contextual triggers.

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