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 burden. The word 'List' conveys a read-only operation, and the description adds that the result includes the measurement ID. It does not disclose expected response shape, pagination, or permissions, though the output schema is present to fill some of that gap.

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?

One sentence, front-loaded with the action and resource, with the measurement-ID detail placed where it adds value. Every word earns its place; there is no filler or repetition of the schema.

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 simple list operation with one optional parameter and an output schema, the description is mostly complete: it names the resource, the scoping property, the key output field, and the common use case. It is only missing an explicit note on property_id format/omission behavior and pointers to how to obtain the property ID.

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%, so the description must compensate. It only says 'on a property,' which identifies the intended scope but does not explain how to format property_id, whether it must match a GA4 property resource name, or what happens when it is omitted (default null). With a single optional parameter, more explicit parameter guidance was needed.

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?

Description opens with a specific verb and resource ('List data streams') and scopes it to 'on a property', clearly distinguishing it from ga4_list_accounts, ga4_list_properties, and the data stream create/update/delete siblings. It also adds the concrete output purpose (measurement ID for GTM tags or gtag.js), making the tool's role unmistakable.

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 gives a clear context for when this tool is useful: when the G-XXXXXXX measurement ID is needed to wire up GTM tags or gtag.js. It does not explicitly name alternatives or exclusion conditions, so it stops short of a full 5.

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