list_key_events

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that the operation is read-only, whether it requires special permissions, if results are paginated, or what happens if the property_id is invalid. The description only states the basic action, leaving the agent to infer behavior.

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 concise sentence, directly front-loaded with the verb and object. Every word serves a purpose, and there is no redundant or filler content.

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?

This is a simple list operation with a single parameter and output schema available, but the description lacks usage context, behavioral details, and any caveats. It is minimally complete for understanding the tool's purpose, but not adequately complete given the lack of annotations and the presence of a create sibling (create_key_event) that could invite confusion.

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?

The schema describes property_id as a required string with no description (0% coverage). The description only mentions 'GA4 property' which is already in the tool description, but does not explain the format of the ID (e.g., numeric vs. 'properties/123'), validation, or its role beyond the obvious. The description adds little meaning beyond the parameter name.

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 'List' with the resource 'key events (conversions)' scoped to a GA4 property. This clearly distinguishes it from sibling tools like create_key_event (create) and other list tools (list_audiences, list_custom_dimensions) by naming the exact resource.

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?

No guidance is provided about when to use this tool versus alternatives. It does not mention that this is the read-only counterpart to create_key_event, nor does it differentiate from run_report for fetching data. The description only states what the tool does, not when to choose it.

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