ga4_data_retention_get

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

With no annotations provided, the description carries the full burden. It explicitly states 'Read-only,' which is a key behavioral trait. It also explains what data is returned. No mention of auth requirements or rate limits, but for a simple read operation, this is adequate.

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 sentence plus 'Read-only,' which is extremely concise and front-loaded. Every part serves the purpose 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?

For a simple tool with one parameter, no annotations, and no output schema, the description is reasonably complete. It explains what the tool does and what it returns. Could optionally detail the output format, but not necessary given the simplicity.

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 100% as the only parameter 'property' has a description in the schema. The description adds context by mentioning 'GA4 property' but does not add 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 clearly states the verb 'Get' and the resource 'data retention settings for a GA4 property', specifying what is returned (event data retention duration and whether retention resets on new activity). This is distinct from sibling tools like ga4_update_data_retention and ga4_property_get.

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 indicates this tool is for reading retention settings, and the 'Read-only' label clarifies safe usage. However, it does not explicitly mention when to use this tool versus alternatives like ga4_property_get or ga4_update_data_retention, though the context of sibling tools suggests it.

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