ga4_list_admin_resources

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

With no annotations provided, the description carries the behavioral disclosure burden. It does state that the operation is 'read-only,' which is a meaningful safety signal. However, it does not disclose pagination behavior, rate limits, access/auth assumptions behind 'allowlisted,' or any result-size limitations beyond what the schema implies.

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, front-loaded sentence that opens with the verb, resource, and read-only nature before enumerating supported collections. The enumeration is long but useful, and no words are wasted, though it could arguably have pointed to the enum instead of repeating the list.

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?

The description is minimally viable for a list operation: it names the resource, covers the main collection categories, and the schema supplies required parameters. But with no annotations and no output schema, the absence of usage guidance, pagination/limitations, and clarity about 'allowlisted' leaves meaningful gaps for an agent deciding whether this is the right tool.

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 50%, with propertyId and includePersonalIdentifiers already documented in the schema. The description's prose list of collection types loosely mirrors the collection enum, adding mild categorization value, but it does not clarify pageSize usage or add meaning beyond what the enum and parameter defaults already provide.

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 a specific verb ('List') with a clear resource ('allowlisted GA4 Admin collection') and enumerates the covered resource types, so an agent understands the tool's scope. It broadly distinguishes itself from sibling list/get tools by covering many admin collections at once, though it does not explicitly name or contrast a sibling.

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?

The description implies when to use the tool—when listing one of the enumerated admin collections—but it gives no explicit guidance on when to prefer this generic lister over specialized siblings like ga4_get_custom_definitions or ga4_get_key_events. There are no exclusions, prerequisites, or alternative-selection criteria.

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