ga4_delete_channel_group

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

No annotations are provided, so the description carries the full burden. It discloses that the tool performs a deletion and requires explicit configuration and confirmation, adding behavioral safeguards beyond the schema.

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 concise sentences: the first states purpose, the second lists requirements. No extraneous information, every word earns its place.

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 single-action delete tool with no output schema, the description covers inputs and necessary conditions. It lacks details on return values or error states, but the simplicity of the operation makes it reasonably complete.

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%, and the description for parameters ('Full resource name...' and 'Must be true to delete') repeats the schema descriptions with no additional semantic value. Baseline score 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 'Delete a custom channel group.' It uses a specific verb and resource, and the '[GA4 DELETE]' prefix distinguishes it from sibling tools like ga4_create_channel_group and ga4_update_channel_group.

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 requirements ('GA4_MCP_ENABLE_DELETES=true and confirm=true'), guiding when the tool is usable. It does not mention alternatives or when not to use, but the required conditions provide clear usage context.

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