ga4_update_data_retention

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

Discloses write operation with GA4 tag and allowed retention values (including 360-only constraint). With no annotations, description carries burden but lacks details on side effects, permissions, or error cases.

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 with parenthetical specifics, front-loaded action, no fluff. Every word adds value.

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?

Covers core behavior and constraints, but omits explanation of confirm parameter's necessity and return value. Could include note that confirm must be true to proceed.

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?

Adds context for eventDataRetention (enum durations in months) and resetUserDataOnNewActivity flag. Schema coverage is 25% (only property described), so description compensates partially; but confirm and property are not further elaborated.

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?

States specific action: 'Update a property's event data retention' with explicit values (2/14/26/38/50 months) and reset flag. Distinguishes from siblings like ga4_data_retention_get and other ga4_update_* tools by naming and constraint details.

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?

Includes prerequisites (writes enabled, confirm=true) but does not specify when to prefer alternatives (e.g., ga4_data_retention_get for reads) or mention non-use cases.

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