ga4_delete_conversion_event

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

With no annotations, the description carries the behavioral disclosure burden. It adds meaningful context by requiring confirm=true and precisely defining event_id as the numeric last path segment of conversionEvents/<id>, not the event name. It could mention irreversibility or permissions, but the confirm requirement and clear action provide adequate 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?

Extremely concise and front-loaded: the core purpose comes first, followed by the critical confirm requirement, then a focused Args block. No filler or redundant restatement of the schema.

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 single-required-parameter delete-style operation, the description covers the essential call requirements. property_id is left undocumented, and side effects are not elaborated, but the presence of an output schema means return values need not be covered.

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 compensates well for event_id by explaining its source, type, and exact location. It also clarifies that confirm must be true. The one gap is property_id, which is not explained at all.

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 states a specific verb ('Un-mark') and resource ('an event as a conversion'), clearly identifying the tool's action. It distinguishes itself from sibling tools like ga4_create_conversion_event and ga4_list_conversion_events by describing the inverse operation.

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?

Gives clear invocation context: confirm must always be true, and event_id must come from ga4_list_conversion_events. It does not explicitly state when-not-to-use or name alternatives, so it stops short of a 5.

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