ga4_delete_expanded_data_set

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

With no annotations, the description carries the full burden. It correctly identifies the operation as destructive and specifies necessary guardrails (env variable and confirm param). However, it does not disclose irreversibility, permission requirements, or what happens to associated data.

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 a single, well-structured sentence that front-loads the action. Every word is necessary, with no filler. The format is efficient and clear.

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 action and critical requirements. It would benefit from a brief explanation of what an expanded data set is, but the tool remains functional as-is. The completeness is adequate given the low complexity.

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 the baseline is 3. The description adds no extra meaning beyond the schema; it reiterates the confirm requirement already present. No examples or additional context are provided.

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 verb 'Delete' and the resource 'expanded data set (360)', making the tool's purpose unambiguous. It distinguishes from sibling tools like ga4_create_expanded_data_set and ga4_update_expanded_data_set through its focus on deletion. However, it does not explicitly differentiate from other delete tools like ga4_delete_account, but the resource name is specific enough.

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 mentions prerequisites (GA4_MCP_ENABLE_DELETES=true and confirm=true) but provides no guidance on when to use this tool versus alternatives like ga4_delete_account or ga4_delete_channel_group. It lacks context for selecting between similar delete tools.

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