list_data_streams

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action (list) and scope (web/app) but does not mention permissions, pagination, rate limits, or output format. The read-only nature is implied but not explicitly confirmed, and no safety characteristics are disclosed.

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: the first states the core functionality, the second provides a practical note about the stream id. Every sentence earns its place with no wasted words, and the structure 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?

The tool is simple, but the missing guidance on property_id format (e.g., 'properties/123' vs '123') and the lack of any safety annotations make it only partially complete. The downstream use case adds useful context, but a format example or explicit read-only hint would be needed for a higher score.

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 one parameter, property_id, with no description at 0% coverage. The description does not mention property_id at all, leaving the agent to infer its meaning solely from the name. This is a significant gap that the description fails to compensate for.

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 (web/app) on a GA4 property, using the specific verb 'List' and resource 'data streams'. It distinguishes from siblings like list_measurement_protocol_secrets by explicitly noting the stream id's role, making its purpose 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 implies usage when a stream id is needed for Measurement Protocol secret tools, providing clear context on when to use this tool. It does not explicitly compare with alternative list tools or state exclusions, so it falls short of a 5.

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