ga4_create_calculated_metric

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

No annotations provided, so the description carries the burden. It flags write intent and confirm requirement, but does not disclose side effects, idempotency, or error conditions. Partial disclosure.

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?

Single sentence effectively conveys purpose and key requirements. No superfluous words, but fails to include additional context that would improve usability without bloating.

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 write operation with 7 parameters and no output schema or annotations, the description is too sparse. It omits return value, error handling, property dependency, and what happens on conflict with existing metric ID.

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 71% leaving some parameters like metricUnit and displayName undocumented. The description adds emphasis on required confirm and calculatedMetricId, but does not explain the 'body' nested object or other fields beyond schema. Adequate but not compensating for gaps.

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 it creates a calculated metric, a specific resource, and includes the required `calculatedMetricId`. The [GA4 WRITE] tag and mention of confirm flag further clarify its operation.

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?

No guidance on when to use this tool over siblings like ga4_update_calculated_metric or ga4_delete_calculated_metric. It only mentions prerequisites (MCP_ENABLE_WRITES, confirm=true) but no context for alternative scenarios.

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