ga4_data_streams_list

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

The description states 'Read-only,' which is a key behavioral trait. However, it does not mention pagination behavior (though the schema describes maxPages and pageToken), rate limits, or any other side effects. With no annotations, the description should provide more behavioral context, but it covers the essential read-only safety.

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 extremely concise: two sentences (with a semicolon) plus a short use-case and read-only note. Every word earns its place with no redundancy. Front-loaded with the verb and resource, it is efficient for an AI agent.

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 tool has 3 parameters, no output schema, and no annotations, the description covers the purpose, types of streams, use case, and safety. It lacks explicit mention of the return format (list of streams) but the schema descriptions for parameters are comprehensive. It is largely complete for a simple list operation.

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 100%, so baseline is 3. The tool description adds context about the return content (measurement IDs, URIs, package names) but does not provide additional meaning for the parameters themselves (property, maxPages, pageToken). It is adequate but not exceptional.

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 tool lists data streams for GA4 properties, specifying types (web, Android, iOS) and what information is included (measurement ID, URI, package name). It effectively distinguishes itself from sibling tools like ga4_properties_list or ga4_custom_dimensions_list, which focus on different resources.

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: 'Use this to audit measurement IDs and stream config.' This gives context for when to employ the tool. However, it does not explicitly state when not to use it or mention alternatives, though the use case is sufficiently clear.

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