ga4_archive_custom_dimension

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

With no annotations, the description carries full burden. It discloses key behaviors: archiving is irreversible, no un-archive, and requires specific conditions. It does not cover error handling or side effects, but for a simple archive operation, this is adequate.

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 (three sentences), front-loaded with a '[GA4 DELETE]' tag for quick categorization, and contains no unnecessary words. Every sentence adds value.

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 no output schema and a simple single-action tool, the description covers the core behavior, prerequisites, and irreversibility. It is nearly complete, though it could mention the return value or confirmation response.

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% for both parameters (name and confirm), and the description adds little beyond what the schema already provides. It confirms confirm must be true, which is also in the schema. 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?

The description clearly states the action ('Archive a custom dimension'), specifies it is a DELETE-like operation, and distinguishes from siblings like ga4_archive_custom_metric by naming the resource. The additional context about no hard delete and permanence further clarifies the purpose.

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 provides explicit prerequisites (GA4_MCP_ENABLE_DELETES=true and confirm=true) and warns of permanence, guiding appropriate use. However, it does not explicitly contrast with alternatives or state when not to use, though the tool is unique among siblings.

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