ga4_delete_data_stream

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

With no annotations, the description carries the full behavioral burden and does so well. It warns that deleting the wrong stream orphans GTM tags/gtag.js calls and that the operation fails silently rather than erroring, which is critical, non-obvious behavior for an agent to know.

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 short sentences, front-loaded with the core purpose and followed by the one indispensable warning. Every clause earns its place; there is no filler or restating of schema fields.

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 description covers the destructive consequence and the required confirm flag, which are the highest-risk aspects of this tool. An output schema exists, so return values need no explanation. The remaining gap is that property_id and stream_id semantics are not addressed, though the tool is otherwise simple enough to invoke correctly.

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 0%, so the description must compensate. It adds real meaning to confirm with 'Always needs confirm=true,' correcting the schema's default false. However, it does not explain stream_id format or the optional property_id parameter, leaving important parameter semantics undocumented.

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 opens with 'Delete a data stream,' stating a specific verb and resource. Among siblings like ga4_create_data_stream, ga4_update_data_stream, and ga4_list_data_streams, this uniquely identifies the deletion operation without needing to parse the schema.

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?

There are no true alternative deletion tools, so 'Delete a data stream' provides the clear context for when to invoke this tool. The explicit 'Always needs confirm=true' adds a hard precondition for calling it. It lacks an explicit when-not-to-use caveat, but none is obviously needed here.

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