ga4_create_calculated_metric

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

Describes the tool as a WRITE operation and flags the need for confirm, but does not disclose error handling, idempotency, rate limits, or response behavior. With no annotations, this is insufficient for an agent to safely invoke.

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?

Extremely concise: one sentence with a clear tag. No wasted words, but the brevity sacrifices completeness. Front-loading is good.

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?

No output schema, so the description should explain return values or side effects. It does not. Also, with 7 parameters, only one is mentioned. The description is incomplete for a create operation.

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 high (71%), so the description adds no new parameter meaning beyond repeating that calculatedMetricId is required. The description does not clarify nested objects or optional fields like body.

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?

Clearly states it creates a calculated metric and mentions the required calculatedMetricId. However, it does not differentiate from sibling tools like ga4_create_custom_metric or ga4_create_audience, which could lead to confusion.

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?

Specifies prerequisites (GA4_MCP_ENABLE_WRITES=true, confirm=true) but lacks guidance on when to use this tool versus other GA4 create tools or alternatives. No explicit when-not-to-use.

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