ga4_create_property

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly warns 'MUTATING', identifies the side effect of creating a web data stream, notes duplicate refusal, and states that dry-run is the default. It omits permissions or quota implications, but the core mutation behavior is transparent.

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, front-loaded sentence that begins with the mutation warning, states the main action, and packs in key behavioral details without filler. Every clause earns its place.

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 the schema covers all parameters and no output schema exists, the description usefully notes the G- measurement ID return value and the dry-run default. It is largely complete, though it leaves some details about expected error behavior or response shape unstated.

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 all five parameters. The description adds some context around display-name duplicates and the returned measurement ID, but it does not substantially enrich parameter meaning beyond what the schema provides.

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 states a specific action and resource: 'Create a GA4 property under an existing Analytics account, plus a web data stream (returns the G- measurement ID).' It clearly distinguishes this from sibling tools that create accounts, profiles, or GTM containers.

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?

It explicitly frames the prerequisite as an existing Analytics account and notes the duplicate display-name refusal, which helps an agent decide when to call it. It does not name an alternative for when no account exists, but the sibling list and prerequisite phrasing provide adequate context.

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