ga4_enhanced_measurement_get

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

The description discloses that the tool is 'Read-only' and mentions the API version ('Admin API v1alpha surface'). With no annotations provided, these behavioral traits are valuable, but the description lacks details on authentication needs, rate limits, or potential side effects.

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 concise at three sentences, front-loading the main purpose. Every sentence adds value without redundancy.

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 output schema, the description adequately lists the types of settings retrieved (scrolls, outbound clicks, etc.) and states it is read-only and web-only. It could mention the return format or structure but is still fairly complete for a getter tool.

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 the schema already documents the two parameters. The description does not add further semantic details beyond mentioning the tool is for web streams, which is a condition, not a parameter.

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 verb 'Get' and the resource 'enhanced measurement settings', and specifies it is for WEB data streams. It lists examples of settings retrieved. While it distinguishes from a potential sibling like ga4_update_enhanced_measurement, it does not explicitly differentiate from other getters.

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 usage for reading enhanced measurement settings and notes the constraint 'Only valid for web streams'. However, it does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools for other data stream types.

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