ga4_archive_custom_metric

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

The description discloses key behavioral traits: 'Archiving is effectively permanent (no un-archive)' and the need for an environment variable. Since no annotations are provided, the description carries full burden and adequately covers irreversibility and prerequisites. It does not explain post-archive effects, but the core behavior is transparent.

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 extremely concise: two sentences plus a tag. It front-loads the action with '[GA4 DELETE]' and wastes no words. Every sentence earns its place, covering action, permanence, and prerequisites efficiently.

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 low complexity (2 required parameters, no output schema), the description covers the action, permanence, and prerequisites. It lacks details on what happens after archiving (e.g., data availability in reports) but is mostly complete for a deletion-like operation. No output schema means description does not need to explain return values.

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 100% (both parameters have clear descriptions). The description adds the global condition about the environment variable but does not elaborate on parameter meanings beyond what the schema provides. Baseline 3 is appropriate as the description adds some context but not significant new info for the parameters.

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 'Archive a custom metric' with the action verb and resource. The '[GA4 DELETE]' tag and mention of 'no hard delete' differentiate it from siblings like ga4_archive_custom_dimension and ga4_update_custom_metric. The purpose is specific and unambiguous.

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 prerequisites: 'Requires GA4_MCP_ENABLE_DELETES=true and confirm=true.' This tells the agent when the tool can be used. However, it does not explicitly state when not to use it or mention alternative tools like ga4_update_custom_metric for non-permanent changes.

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