ga4_delete_key_event

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

No annotations provided, so the description carries full burden. It discloses that deletion returns the key event to a normal event and requires a confirm parameter and an environment variable. However, it does not detail consequences like irreversibility or error handling.

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?

Extremely concise: one line with a clear prefix, action, and requirements. Every part is essential and front-loaded.

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 tool is a delete operation with a confirmation flag and an environment variable requirement, the description covers the key points. No output schema exists, but the return is likely minimal. Could mention success/failure indication, but not critical.

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% with descriptions for both parameters. The description reinforces that confirm must be true but does not add meaning beyond the schema. The requirement for GA4_MCP_ENABLE_DELETES is an additional constraint not in 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?

The description clearly states the action ('Delete a key event') and the effect ('reverts to a normal event'). It distinguishes itself from sibling tools like ga4_create_key_event and ga4_update_key_event by specifying it is a delete operation with a [GA4 DELETE] prefix.

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 explicitly lists the prerequisites: 'Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.' This guides the agent on when the tool can be invoked. It does not explicitly mention when not to use it, but the context is clear.

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