ga4_create_data_stream

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

With no annotations, the description only identifies it as a write operation requiring confirmation. It does not disclose idempotency, error conditions, permission scope, or consequences (e.g., quotas, duplication).

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?

Two sentences, front-loaded with purpose and critical requirements. Zero extraneous text.

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?

No output schema or description of return value. For a write tool, what the agent should expect after creation (e.g., the new stream object) is missing, leaving the agent guessing about the response format.

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 coverage is 88% with good parameter descriptions. The tool description adds little beyond restating stream types and the confirm requirement, which are already clear from the schema.

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?

Clearly states action (create), resource (data stream), and types (web/Android/iOS). The GA4 WRITE tag and sibling tools help distinguish from list/update/delete operations.

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?

Explicitly mentions required prereqs (GA4_MCP_ENABLE_WRITES=true, confirm=true) but does not state when to avoid or specify alternatives beyond implied context from sibling tools.

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