ga4_list_data_streams

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It implies a read-only listing operation but does not disclose pagination behavior, result ordering, required authentication scope, or whether data streams are nested under a specific property. No mention is made of quotas, errors, or return characteristics.

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 with no filler, which is concise. However, it is under-sized relative to the operational details an agent would need, so the brevity comes at the cost of completeness.

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?

With no output schema and no annotations, the description should explain what the response contains, how pagination is controlled, and how this call fits into the GA4 workflow. None of that is present, leaving the tool only minimally viable for an agent deciding whether and how to invoke it correctly.

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 only 33%: pageSize and pageToken lack descriptions entirely. The description adds no detail about these two parameters or how pagination works, and it only minimally reinforces that propertyId identifies the GA4 property whose streams should be listed.

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 names a specific verb ('Lists') and a distinct resource ('data streams') with an explicit scope ('for a GA4 property'), which is enough to distinguish it from account-level and property-level listing tools. It does not explicitly name sibling alternatives, so it stops short of a perfect differentiation.

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 ga4_list_properties, ga4_get_property, or other GA4 list tools. The intended context is only implied by the tool's name and one-line description, with no mention of alternatives, required prerequisites, or follow-up actions.

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