ga4 get property configuration

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is clear without description help. The description's 'Read' verb reinforces non-mutation and the phrase 'selected singleton Admin settings' adds some context about the data source, but no additional behavioral traits such as auth needs, rate limits, or empty-result behavior are disclosed. Given strong annotation coverage, this is adequate but not additive.

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 with no filler; the action ('Read') and subject ('GA4 property details plus...') are front-loaded. It earns its place, though the phrase 'selected' is somewhat vague without the parameter context.

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?

The tool is simple with one required string parameter and one optional array with enum, has a full input schema, rich annotations, and an output schema, so the description does not need to detail outputs. The one-line description plus structured data is sufficient for an agent to invoke it. A minor gap is not explaining what happens when 'settings' is omitted, but the schema default [] covers this.

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. The description lists the same five settings values that appear in the schema enum, adding little new information; the term 'singleton Admin settings' is the only added semantic. This falls at the baseline 3 because the schema carries the parameter semantics.

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 the verb 'Read' and identifies a specific resource: GA4 property details plus selected singleton Admin settings (attribution, retention, Google Signals, reporting identity, or user-provided-data settings). The explicit enumeration of settings distinguishes this from broader tools like ga4_list_properties or ga4_list_admin_resources, though it does not name a sibling directly.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, state when not to use it, or point to related tools for listing properties or admin resources. The intended use is only implied by the tool name and read-only nature.

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