ga4_list_conversion_events

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

With no annotations, the description carries the behavioral disclosure burden. It usefully reveals that deleted events can appear briefly with countingMethod unset during propagation, which is non-obvious and valuable. It does not mention permissions or rate limits, but for a simple list operation the disclosed caveat is meaningful.

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 compact sentence that front-loads the core purpose and then adds useful detail. Every clause earns its place, with no filler or repetition.

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 low-complexity list tool with one optional parameter and an output schema, the description covers what is returned (custom/default status, counting status) and includes a relevant edge case. It lacks explicit usage guidance, but the remaining context is sufficiently 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?

Schema description coverage is 0%, so the description must compensate for the undocumented property_id parameter. It only says 'on a property', which adds minimal meaning beyond the parameter title and does not explain the expected format, whether it's required, or how it maps to the GA4 property.

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 uses a specific verb ('List') and resource ('conversion events (Key events) on a property') and adds the distinguishing elements of custom vs default and counting status. This clearly separates it from sibling mutation tools like ga4_create_conversion_event and ga4_delete_conversion_event.

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 gives no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of related tools such as ga4_create_conversion_event or ga4_delete_conversion_event. Usage context is only implied by the word 'List' and the sibling names.

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