ga4_delete_data_stream

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

Discloses the consequence of deletion (removes measurement ID / firebase app id) and the required confirm flag. With no annotations, the description does not address permissions, data permanence, or side effects beyond the immediate effect.

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?

Single sentence with a clear prefix and all essential information. No superfluous words; every phrase earns its place.

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?

For a simple delete tool with two parameters and no output schema, the description covers the core purpose, prerequisites, and effect. Missing return value or error cases are acceptable for a destructive 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 coverage is 100%, so both parameters are already described in the input schema. The description adds minimal value by repeating the confirm requirement. Baseline 3 is appropriate.

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 the action 'Delete a data stream' and specifies what is removed ('measurement ID / firebase app id'). The '[GA4 DELETE]' prefix distinguishes it from other GA4 tools.

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 lists prerequisites: 'Requires GA4_MCP_ENABLE_DELETES=true and confirm=true'. Does not compare to other delete tools or provide when-not-to-use guidance, but the requirements are clear enough for safe invocation.

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