list_property_annotations

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety bar is covered. The description adds genuinely useful behavior beyond that: you must follow nextPageToken even on empty pages, filters must stay identical across pages, and annotation notes are untrusted context rather than causal proof.

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?

Three short lines with zero filler; the resource and paging rule lead, syntax example follows, and the caveat closes. The parenthetical '(Admin v1alpha)' is the only mildly opaque fragment.

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?

An output schema exists so return values need no explanation, and pagination is well covered. However, for a 5-parameter tool with no schema descriptions, the definition leaves property_id scoping, account selection, and page_size defaults entirely unaddressed.

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% across 5 parameters, so the description carries the burden and only partly does: it explains the filter's Google-style syntax with a concrete is_annotation_in_range example and ties page_token paging to filter stability. account, page_size, and property_id receive no semantic elaboration anywhere.

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: 'Read dated annotations (Admin v1alpha)'. That is clearly distinguishable from reporting siblings like run_report or get_summary, though it never says these are GA4 property-level annotations or how they differ from search_change_history.

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 implied through the filter example (date-range annotations) and the paging instruction, but there is no explicit statement of when to reach for this tool versus the many reporting siblings, and no note on required scope or a property_id default.

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