ga4_resolve

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does reveal the default behavior when measurement_id is omitted and describes the resolution transformation, but it does not state whether the operation is read-only, whether authentication is required, or what happens on failure.

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 a single, focused sentence with no wasted words. It front-loads the core transformation and efficiently appends the default-value behavior.

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?

Given no annotations, no output schema, and three undocumented parameters, the description is too thin. It omits the purpose of the authentication/context parameters and does not specify the exact return structure beyond 'numeric property_id + stream', which is insufficient for reliable agent use.

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 0%, so the description must compensate, but it only clarifies the measurement_id parameter and its default. The connection_id and session_token parameters are left entirely unexplained in both the schema and the description, leaving the agent to guess their roles.

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 ('Resolve') and a defined resource ('GA4 measurement id'), and states the concrete output: numeric property_id + stream. The GA4 prefix and example clearly distinguish it from the sibling gtm_resolve tool.

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 implies the tool should be used when converting a GA4 measurement ID into a numeric property ID and stream. However, it does not explicitly state when to use it over alternatives like ga4_list_data_streams or ga4_get_property, and gives no exclusion criteria.

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