ga4_list_conversion_events

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It simply restates a read operation without explicitly confirming the read-only nature, explaining that pageSize/pageToken enable pagination, or noting any authorization requirements.

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 efficient sentence with no redundant words and is well front-loaded. However, its brevity leaves behavioral and parameter details to be filled by other sources.

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?

With no output schema and no annotations, a complete description should clarify what a conversion event is, whether the response is paginated, and what the return payload contains. The current text only restates the tool name's meaning and leaves these key details unspecified.

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 only 33%, with propertyId described only as 'GA4 Property ID'. pageSize and pageToken lack descriptions, and the tool description does not compensate by explaining how pagination works or what propertyId targets.

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 the specific verb 'Lists' with the resource 'conversion events' scoped to 'a GA4 property'. This clearly distinguishes it from sibling list tools such as ga4_list_custom_dimensions, ga4_list_data_streams, and ga4_list_audiences.

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?

There is no guidance about when to use this tool versus alternatives, nor any exclusions or related tool suggestions. For example, it does not clarify that ga4_run_report is more appropriate for querying conversion metrics rather than listing configured conversion event names.

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