ga4_archive_audience

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

No annotations are provided, so the description carries the burden. It discloses that archiving is effectively permanent and irreversible. However, it does not describe side effects on related data or whether the audience is entirely removed from reports. The mention of 'stops collection' is helpful but lacks depth for a mutation tool.

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?

Two sentences deliver all essential information: purpose, permanence, prerequisites. No extraneous text. The [GA4 DELETE] prefix clearly signals it is a destructive operation. Excellent conciseness.

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 tool with two required parameters and no output schema, the description covers purpose, permanence, and configuration needs. It does not explain the response or further effects, but the simplicity of the operation makes this acceptable. Slightly better completeness would address what happens to the audience data after archiving.

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%, so the schema already documents both parameters. The tool description reinforces that confirm must be true and that name is a resource name, but adds no new detail beyond schema. Baseline 3 for high coverage.

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 tool archives an audience, stopping collection, and emphasizes permanence. The verb 'archive' distinguishes it from delete tools like ga4_delete_property, and the parenthetical 'no un-archive' sets clear expectations.

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 requires GA4_MCP_ENABLE_DELETES=true and confirm=true, giving clear prerequisites. It does not list alternative tools for un-archiving, but the permanent nature inherently advises caution. Could be improved by stating when not to use (e.g., if re-activation might be needed).

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