ga4 validate query

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail about the specific validation rules enforced (9 dims, 10 metrics, ecommerce rules, dimension compatibility), going beyond what annotations alone provide.

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?

A single dense sentence front-loads the purpose ('Validate BEFORE executing') and lists the specific checks without any filler or redundant restatement of the title. Every clause 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 straightforward two-parameter validation tool with a full output schema and strong annotations, the description covers what the tool checks and when to run it. Minor gaps remain, such as clarifying the result/response shape, but the output schema can carry that burden.

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 both parameters are already documented ('Metric keys to validate' and 'Dimension keys to validate'). The description adds the validation context and limits but does not add parameter-level meaning beyond the schema. Baseline 3 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 uses a specific verb, 'Validate', names the resource ('a metric/dimension combination'), and states the functional scope: max limits, ecommerce rules, and dimension compatibility. This clearly distinguishes it from execution tools like ga4_run_report and from diagnostic sibling tools.

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 positions the tool as a pre-execution gate ('BEFORE executing'), which is clear usage context. However, it does not mention exclusions or explicitly differentiate from the closely named sibling ga4_check_compatibility, so it stops short of full guidance.

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