ga4_datastreams_get

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

With no annotations, description must fully convey behavior. The word 'list' implies a read-only operation, which is transparent enough for a simple list. However, it doesn't disclose pagination, authentication requirements, or the nature of the returned data, leaving some gaps.

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, seven words, no fluff. Essential information is front-loaded. Ideal conciseness for a simple list tool.

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 output schema and annotations, the description is minimal but functional. It doesn't describe the return format (e.g., array of stream objects), pagination, or any edge cases. Adequate for a straightforward list, but would benefit from slight expansion.

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 single parameter 'property_id' has no schema description (0% coverage). The description adds value by stating 'of a property', clarifying that property_id identifies the property whose data streams are listed. This compensates for the missing schema description.

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 clearly states the tool lists data streams of a property, using a specific verb and resource. It differentiates from siblings like ga4_datastream_get (singular) and ga4_datastream_create, but could be more explicit about the 'list' vs 'get' distinction.

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?

No guidance on when to use this tool versus alternatives (e.g., ga4_datastream_get for a single stream, or ga4_datastream_create for creation). The description provides no context about prerequisites or typical use cases.

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