ga4_delete_calculated_metric

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

No annotations are provided, so the description must convey behavioral traits. It correctly highlights the mandatory flag and confirmation parameter, but omits critical details such as whether the operation is irreversible, permission requirements, or error handling scenarios.

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 short sentences—with no redundant information. Every word serves a purpose, and it is front-loaded with the action and key prerequisites.

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 simple delete tool with two parameters and no output schema, the description adequately explains the core usage constraint (flag + confirm). However, it lacks information about expected outcomes (e.g., success message, errors) and permissions, which could leave the agent uncertain about post-invocation behavior.

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?

The input schema already covers both parameters (name and confirm) with descriptions. The description adds value by combining the tool-level requirement (GA4_MCP_ENABLE_DELETES= true) with the confirm parameter, reinforcing that confirm must be true for the operation to succeed.

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 calculated metric') and resource. While it does not explicitly differentiate from sibling delete tools, the name already implies the resource type, and the description is 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 provides prerequisites (GA4_MCP_ENABLE_DELETES flag and confirm=true), which helps the agent understand when the tool will work. However, it offers no guidance on when not to use it or alternatives like ga4_update_calculated_metric for modifications.

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