ga4_change_history

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

With no annotations at all, the description carries the full burden and does meaningful work: it names the API that must be enabled on the quota project, the required GA4 role (Editor/Admin), and the OAuth scope analytics.edit, plus how failures surface. It omits result limits, pagination, and retention window of the change log, which keeps it out of the top band.

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 purpose is front-loaded in the first clause and the prerequisites follow in a compact second sentence; nothing is wasted. However, the phrase "Editor o Administrador en la cuenta de GA4" mixes Spanish into an otherwise English description, which slightly hurts scannability.

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 two-parameter read tool with no output schema, the definition covers what is returned conceptually (who changed what and when), the prerequisites, and the failure path. The main remaining gap is that it does not indicate volume or time-bound behavior of the change log, which an agent would want before calling it.

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 100%, so both parameters (days with its 1-365 bounds and default of 30, property pointing at ga4_list_properties) are already documented in the schema. The description adds nothing about how many days are useful or how property resolution behaves, so the baseline of 3 applies.

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?

"Recent configuration changes in the property: who changed what and when" states a specific resource (change history / audit events) and names the backing API call (searchChangeHistoryEvents), which cleanly separates it from the reporting siblings like ga4_run_report or ga4_event_counts. It stops short of naming a sibling it is explicitly not, so it falls just below the top band.

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?

It gives a clear context of use (auditing who changed configuration) and routes the agent elsewhere for the related prerequisite: "ga4_check_access checks everything at once," plus "If it fails for access, the error explains how to fix it." No explicit when-not-to-use case is given, so it is clear but not fully exclusionary.

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