ga4_data_streams_list

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

No annotations are provided, so the description carries the full burden. It declares the tool as 'Read-only', implying no side effects. It also mentions pagination behavior (truncated:true, nextPageToken) and the types of data returned per stream. This is good coverage for a listing endpoint, though authentication or rate limits are not mentioned.

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 two sentences, front-loaded with the main purpose, and every word adds value. It avoids redundancy, is well-structured, and fits the tool's simplicity.

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?

Given the absence of an output schema and annotations, the description provides key behavioral details (read-only, pagination) and clarifies what each stream type includes. It does not cover error cases or authorization requirements, but for a straightforward list operation, this is reasonably complete.

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 input schema has 100% coverage with descriptions for all three parameters. The description does not repeat parameter details but adds value by explaining the output structure (web streams include measurement ID/URI, app streams include package name/bundle ID). Since the schema already documents parameters, a baseline of 3 is appropriate; the description enriches understanding of the return data, not the parameters themselves.

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 clearly states the verb 'List', the resource 'data streams for a GA4 property', and specifies three stream types (web, Android, iOS). It distinguishes itself from sibling tools like ga4_create_data_stream or ga4_delete_data_stream by focusing purely on listing.

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 provides a clear use case: 'audit measurement IDs and stream config'. Although it doesn't explicitly list when not to use or compare with alternatives, the read-only annotation and the listing focus imply it's safe and appropriate for inspection. A more explicit exclusion would be ideal, but current guidance is sufficient.

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