ga4_list_data_streams

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds useful context by scoping the list to web/iOS/Android streams and mentioning creation/update timestamps, but it does not disclose pagination, rate limits, or how many streams are returned. This matches the expected level for a read-only list with annotation coverage.

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 tight sentences: the first states the operation, the second gives practical lookup purposes, and the third adds timestamp behavior. There is no filler or redundant restating of the tool name. The most important information is front-loaded.

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 an output schema and read-only annotations, the description is largely complete. It clearly states scope, common use cases, and available metadata fields. The only notable gaps are property_id format details and explicit pagination/limit behavior, but these are minor given the low complexity and existing annotations/output schema.

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?

The schema has 0% description coverage for property_id, so the description carries the burden. It does tie the parameter to 'a GA4 property,' adding minimal semantic context beyond the schema's bare 'Property Id' title. However, it does not specify the expected format (e.g., numeric property ID vs. resource path), so the parameter guidance is incomplete but adequate for a single obvious required parameter.

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 opens with a specific verb and resource: 'List all data streams (web, iOS, Android) on a GA4 property.' It clearly distinguishes this from sibling list tools by naming the exact resource type and the platform variants. There is no ambiguity about what the tool operates on.

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 concrete use cases: finding Measurement ID, firebase_app_id, hostname, and timestamps. It implies 'use this when you need data stream identifiers or metadata,' which is clear context. It does not explicitly mention exclusions or sibling alternatives, but the sibling tools are all different GA4 resources, so the usage context is sufficient.

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