GA4: Annotations

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-API behavior are covered. The description adds real value beyond that by disclosing the sort order ("Newest first") and the nature of the returned items, but says nothing about pagination, result limits, or what happens when a property has no annotations.

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?

A single front-loaded sentence with the verb and resource first, followed by clarifying examples and ordering. Every clause earns its place; the only minor cost is that the examples lengthen the sentence without aiding invocation.

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 one-parameter read-only list tool with annotations and an adequate schema, the description covers what is returned, what annotations represent, and the ordering. Pagination and empty-result behavior are the only notable omissions, and neither is critical for correct invocation.

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?

There is a single required parameter with 100% schema description coverage, including accepted ID formats ('123456789' or 'properties/123456789'), so the schema carries parameter meaning fully. The description only implies the property argument via "of a property" and adds no format or constraint detail beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ("Lists the annotations of a property") and clarifies what a GA4 annotation is with concrete examples (relaunch, GTM publish, campaign start), plus the result ordering. It implicitly separates itself from ga4_create_annotation by being a read/list, but never names the sibling explicitly, so it falls just short of a 5.

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?

Usage is only implied: an agent can infer you call this to inspect existing annotations on a property. There is no explicit when-to-use, no when-not-to-use, and no pointer to related tools such as ga4_create_annotation for creating one or ga4_change_history for other change records.

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